asakasinsky

# https://download.docker.com/linux/debian/dists/buster/pool/stable/armhf/

# containerd.io_1.3.7-1_armhf.deb
wget https://download.docker.com/linux/debian/dists/buster/pool/stable/armhf/containerd.io_1.3.7-1_armhf.deb
wget https://download.docker.com/linux/debian/dists/buster/pool/stable/armhf/docker-ce-cli_19.03.9~3-0~debian-buster_armhf.deb
wget https://download.docker.com/linux/debian/dists/buster/pool/stable/armhf/docker-ce_19.03.9~3-0~debian-buster_armhf.deb
sudo dpkg -i ./containerd.io_1.3.7-1_armhf.deb
sudo dpkg -i ./docker-ce-cli_19.03.9~3-0~debian-buster_armhf.deb
sudo dpkg -i ./docker-ce_19.03.9~3-0~debian-buster_armhf.deb
# add current user to docker group

asakasinsky

FROM docker.io/library/docker:dind

RUN apk --update add \
    bash \
    py-pip \
    supervisor \
    openssh \
    curl \
    build-base \
    libffi-dev \

asakasinsky

# docker image with elixir, docker, docker-compose

FROM elixir:1.9.4

RUN set -ex \
  && export DOCKER_VERSION=$(curl --silent --fail --retry 3 https://download.docker.com/linux/static/stable/x86_64/ | grep -o -e 'docker-[.0-9]*\.tgz' | sort -r | head -n 1) \
  && DOCKER_URL="https://download.docker.com/linux/static/stable/x86_64/${DOCKER_VERSION}" \
  && echo Docker URL: $DOCKER_URL \
  && curl --silent --show-error --location --fail --retry 3 --output /tmp/docker.tgz "${DOCKER_URL}" \
  && ls -lha /tmp/docker.tgz \

asakasinsky

Docker cheatsheet, usually has one-lines to delete containers.

• Create a image from docker file: docker build -t image-name .
• Run a container: docker run -it --name container-name image-name:latest
• Run docker in backgroud: docker run --name container-name --hostname container-hostname -t -d container-name:latest
• Connect to container: docker exec -it container_name bash
• Remove all Exited containers: sudo docker ps -a | grep Exit | cut -d ' ' -f 1 | xargs sudo docker rm
• Remove all dangling images: docker rmi $(docker images -f 'dangling=true' -q)

asakasinsky

docker rm -v $(docker ps -a -q -f status=exited)
docker rmi $(docker images -f "dangling=true" -q)
docker volume rm $(docker volume ls -qf dangling=true)

asakasinsky

# list Virtual IP address of all services (from master node)
docker service ls --format "{{.Name}}" | xargs -I{} docker inspect {} -f "{{.Spec.Name}} - {{.Endpoint.VirtualIPs}}"

asakasinsky

#/bin/bash

set -e

brew install colima
brew install docker
pip3 install docker-compose

colima start

asakasinsky

# sudo socat -v UNIX-LISTEN:/tmp/dockerapi.sock,fork UNIX-CONNECT:/var/run/docker.sock

# docker -H unix:///tmp/dockerapi.sock ps -a

asakasinsky

#Exemple Issu de docker-compose

version: "3"
networks:
    dev_traefik:
       external: true
services:
    wordpress:
            #image: wordpress:latest
        build:

asakasinsky

Jenkins in Docker (docker-in-docker)

Testing Jenkins flows on your local machine, or running Jenkins in production in a docker container can be a little tricky with a docker-in-docker scenario. You could install Jenkins to avoid any docker-in-docker issues, but then you have Jenkins on your machine, and the local environment is likely going to be a fairly different from the actual production build servers, which can lead to annoying and time-consuming issues to debug.

Build environment differences are precisely why there is a strong argument to be made to run build processes strictly in docker containers. If we follow the philosophy that every build step or action should run in a docker container, even the Jenkins server itself, then we get massive benefits from things like, total control over the build environment, easily modify the build environment without the possibility of adversely effecting other jobs, explicit and strongly controlled tool versions,