Chapter 8: Don't `chown 777 /var/run/docker.sock`

Hi @danielclough ,

That's correct for a Linux host, in fact it's documented in the installation pages (Docker official documentation). If I'm not wrong, the instructor was running Docker on macOS, and that may not work in the same way (for macOS you use Docker Desktop).

Anyway it's not a recommended way for macOS as well. We'll take a look to this.

Regards,
Luis.

Here is sample script

Yes but still not working, can you please let me know how I can modify group file on the docker host and jenkins docker. I am using ubuntu 18.04. appreciate your help.

@cziaul The instructor will get back to you as soon as possible. We appreciate your patience.

@cziaul please re run the following commands inside the container

usermod -a -G docker jenkins

chmod 777 /var/run/docker.sock

I just tested setting a brand new environment with ubuntu as the host, with docker installed and by setting up a jenkins container from scratch.

Running the script in Lab 6 did the job for me. Above snippet is from the same script. For your reference, this is how my /etc/group files on the host and inside the containers look like

host

docker:x:998:

container (jenkins)

docker:x:999:jenkins

when I run docker command from inside jenkins container, it works as expected

 docker ps
CONTAINER ID        IMAGE                        COMMAND                  CREATED             STATUS              PORTS                                              NAMES
f5e2600df555        jenkins/jenkins:2.178-slim   "/sbin/tini -- /usr/…"   19 minutes ago      Up 19 minutes       0.0.0.0:8080->8080/tcp, 0.0.0.0:32768->50000/tcp   jenkins
49df246c7323        k8s.gcr.io/coredns           "/coredns -conf /etc…"   11 hours ago        Up 11 hours                                                            k8s_coredns_coredns-f9fd979d6-tvj25_kube-system_c8597f47-74ff-4812-a7b7-5429c8fe4fcf_0

@cziaul and @danielclough ,

An even cleaner approach to setup docker along with jenkins is to use a DIND container. That would completely eliminate the need to do the socket mount which has inherent risks. This approach is documented here https://www.jenkins.io/doc/book/installing/docker/.

I have adapted this approach and created a docker compose file which I have been using for my CI/CD workshops and bootcamps since last few months. I am sharing it here. You may find this useful.

Filename: docker-compose.yaml

version: '3.0'

networks:
  custom:
    driver: bridge
    ipam:
      driver: default
      config:
        - subnet: 192.168.61.0/24

volumes:
  jenkins-docker-certs:
  jenkins-data:

services:
  jenkins:
    image: jenkinsci/blueocean
    ports:
      - 8080:8080
      - 50000:50000
    environment:
      - DOCKER_HOST=tcp://docker:2376
      - DOCKER_CERT_PATH=/certs/client
      - DOCKER_TLS_VERIFY=1
    networks:
      custom:
        ipv4_address: 192.168.61.15
    dns: 8.8.8.8
    domainname: codespaces.io
    hostname: jenkins
    restart: always
    volumes:
      - jenkins-data:/var/jenkins_home
      - jenkins-docker-certs:/certs/client:ro
    depends_on:
      - docker

  docker:
    image: docker:dind
    ports:
      - 2376:2376
    environment:
      - DOCKER_TLS_CERTDIR=/certs
    networks:
      custom:
        ipv4_address: 192.168.61.16
        aliases:
          - docker
    privileged: true
    domainname: codespaces.io
    hostname: docker
    restart: always
    volumes:
      - jenkins-docker-certs:/certs/client
      - jenkins-data:/var/jenkins_home