Chapter 8: Don't `chown 777 /var/run/docker.sock`
In the lab for 08. Using Docker with Jenkins Pipelines it is suggested to chown 777 /var/run/docker.sock
, which is noted as "not recommended".
In the beginning of the course the instructor said that learning too many things makes problems, and I agree, but if you already have a foundation in Linux SysAdmin... the likely problem is not that complicated.
A more elegant solution is to make the /etc/group files match on the host system and within the container.
Example:
[email protected]$ tail /etc/group
...
docker:x:1001:daniel
[email protected]# tail /etc/group
...
docker:x:999:jenkins
Just make those numbers match and you should be golden.
Comments
-
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.1 -
Hi, can you please explain more how both can be same, I am getting below error
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 3: Invalid agent type "docker" specified. Must be one of [any, label, none] @ line 3, column 9.
docker {
^1 error
at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.
Also when I type docker ps, I get below
This is outside container
Appreciate any help
0 -
Here is sample script
0 -
@danielclough your approach of modifying the groups file on the docker host is definitely cleaner. However, I still had the chmod 777 in the course based on my experience of teaching this to over 60k students because from my observations,
- Not everyone uses linux as the host os. In fact, majority of the students who take this course either setup docker with Windows/Mac OS.
- Even though considered fundamentals, not everyone has systems knowledge. This course it also relevant for developers and QA who do not want to fiddle with the underlying system and prefer a easier, canned approach.
Having said that, to make it easier, I would add the following to the script
usermod -a -G docker jenkins
This provides a cleaner approach, yet can be provided as canned commands as part of the script.
@cziaul you seem to have added jenkins user already. Have you tried restarting the jenkins container ?
docker restart jenkins
0 -
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.
0 -
Can I please get an answer on this?
0 -
I am presently getting permission denied msg
0 -
@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
0 -
@gouravshah Thanks for the reply, I think what danielclough mentioned above is a cleaner approach and since I am applying above at my work, can you please let me know how I can do it more secure way without applying 777. Appreciate your help.
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
1
Categories
- 10.1K All Categories
- 35 LFX Mentorship
- 88 LFX Mentorship: Linux Kernel
- 504 Linux Foundation Boot Camps
- 279 Cloud Engineer Boot Camp
- 103 Advanced Cloud Engineer Boot Camp
- 48 DevOps Engineer Boot Camp
- 41 Cloud Native Developer Boot Camp
- 2 Express Training Courses
- 2 Express Courses - Discussion Forum
- 1.8K Training Courses
- 17 LFC110 Class Forum
- 5 LFC131 Class Forum
- 19 LFD102 Class Forum
- 148 LFD103 Class Forum
- 13 LFD121 Class Forum
- 61 LFD201 Class Forum
- LFD210 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 23 LFD254 Class Forum
- 569 LFD259 Class Forum
- 100 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFS145 Class Forum
- 23 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 1 LFS203 Class Forum
- 45 LFS207 Class Forum
- 298 LFS211 Class Forum
- 53 LFS216 Class Forum
- 46 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 10 LFS244 Class Forum
- 27 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- 131 LFS253 Class Forum
- 997 LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 87 LFS260 Class Forum
- 126 LFS261 Class Forum
- 31 LFS262 Class Forum
- 79 LFS263 Class Forum
- 15 LFS264 Class Forum
- 10 LFS266 Class Forum
- 17 LFS267 Class Forum
- 17 LFS268 Class Forum
- 21 LFS269 Class Forum
- 200 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 212 LFW211 Class Forum
- 153 LFW212 Class Forum
- 899 Hardware
- 217 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 208 Networking
- 101 Printers & Scanners
- 85 Storage
- 749 Linux Distributions
- 88 Debian
- 64 Fedora
- 14 Linux Mint
- 13 Mageia
- 24 openSUSE
- 133 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 355 Ubuntu
- 473 Linux System Administration
- 38 Cloud Computing
- 69 Command Line/Scripting
- Github systems admin projects
- 94 Linux Security
- 77 Network Management
- 108 System Management
- 49 Web Management
- 63 Mobile Computing
- 22 Android
- 27 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 528 Off Topic
- 127 Introductions
- 213 Small Talk
- 20 Study Material
- 794 Programming and Development
- 262 Kernel Development
- 498 Software Development
- 923 Software
- 258 Applications
- 182 Command Line
- 2 Compiling/Installing
- 76 Games
- 316 Installation
- 53 All In Program
- 53 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)