Docker socket mounting in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Docker socket mounting in the context of Jenkins?

Docker socket mounting means connecting the Docker engine's communication socket from the host machine into the Jenkins container. This allows Jenkins to run Docker commands directly on the host's Docker engine.

beginner

Why do we mount the Docker socket into a Jenkins container?

Mounting the Docker socket lets Jenkins control Docker on the host. This means Jenkins can build, run, and manage Docker containers without installing Docker inside the Jenkins container itself.

beginner

What is the typical Docker socket file path mounted into Jenkins?

The Docker socket file path is usually /var/run/docker.sock on the host. It is mounted into the Jenkins container at the same path to allow communication.

intermediate

Show the Docker run command snippet to start Jenkins with Docker socket mounted.

docker run -d -v /var/run/docker.sock:/var/run/docker.sock -p 8080:8080 jenkins/jenkins

intermediate

What is a security consideration when mounting the Docker socket into Jenkins?

Mounting the Docker socket gives Jenkins full control over the Docker engine and host system. If Jenkins or its plugins are compromised, attackers can control the host. So, it should be done carefully with trusted code.

What does mounting /var/run/docker.sock into Jenkins allow?

A Jenkins to run on a different port

B Jenkins to run Docker commands on the host

C Jenkins to store logs persistently

D Jenkins to access the internet

Mounting the Docker socket allows Jenkins to communicate with the host's Docker engine and run Docker commands.

Which Docker run option mounts the Docker socket into a container?

A --network host

B -p 8080:8080

C -v /var/run/docker.sock:/var/run/docker.sock

D -e DOCKER_HOST=/var/run/docker.sock

The -v option mounts volumes. Here it mounts the Docker socket file from host to container.

What risk comes with mounting the Docker socket into Jenkins?

A Jenkins can control the host Docker engine, risking security

B Jenkins can crash easily

C Jenkins loses network access

D Jenkins cannot build Docker images

Mounting the Docker socket gives Jenkins full control over Docker on the host, which can be a security risk if Jenkins is compromised.

If you want Jenkins to build Docker images, what is a simple way to enable this?

A Mount the Docker socket into Jenkins container

B Install Docker inside Jenkins container

C Use Jenkins without Docker

D Run Jenkins on a different port

Mounting the Docker socket allows Jenkins to use the host's Docker engine to build images without installing Docker inside Jenkins.

What is the default path of the Docker socket on Linux hosts?

A /home/docker.sock

B /etc/docker.sock

C /usr/bin/docker.sock

D /var/run/docker.sock

The Docker socket is usually located at /var/run/docker.sock on Linux systems.

Explain how mounting the Docker socket helps Jenkins run Docker commands.

Think about how Jenkins talks to Docker without installing Docker inside itself.

Describe the security risks of mounting the Docker socket into Jenkins and how to mitigate them.

Consider what happens if someone bad controls Jenkins with Docker socket access.

Practice

1. What is the main purpose of mounting the Docker socket /var/run/docker.sock inside a Jenkins container?

easy

A. To allow Jenkins to control Docker on the host machine

B. To increase Jenkins container storage space

C. To isolate Jenkins from the host Docker engine

D. To enable Jenkins to run without Docker installed

Solution

1. Step 1: Understand Docker socket mounting

   Mounting /var/run/docker.sock lets a container communicate with the host's Docker engine directly.

2. Step 2: Apply to Jenkins use case

   Jenkins uses this to build and run Docker containers on the host from inside its own container.

3. Final Answer:

   To allow Jenkins to control Docker on the host machine -> Option A

4. Quick Check:

   Docker socket mounting = Jenkins controls host Docker [OK]

Hint: Docker socket mounting = container controls host Docker [OK]

Common Mistakes:

• Thinking it increases container storage
• Assuming it isolates Jenkins from Docker
• Believing it removes need for Docker installation

2. Which of the following is the correct Docker run command snippet to mount the Docker socket inside a Jenkins container?

easy

A. docker run -v /var/run/docker.sock:/var/run/docker jenkins

B. docker run -v /var/run/docker.sock:/docker.sock jenkins

C. docker run -v /docker.sock:/var/run/docker.sock jenkins

D. docker run -v /var/run/docker.sock:/var/run/docker.sock jenkins

Solution

1. Step 1: Identify correct volume mount syntax

   The syntax is -v host_path:container_path. The Docker socket is at /var/run/docker.sock on the host and must be mounted to the same path inside the container.

2. Step 2: Match correct paths

   docker run -v /var/run/docker.sock:/var/run/docker.sock jenkins correctly mounts /var/run/docker.sock from host to container at the same path.

3. Final Answer:

   docker run -v /var/run/docker.sock:/var/run/docker.sock jenkins -> Option D

4. Quick Check:

   Correct volume mount syntax = docker run -v /var/run/docker.sock:/var/run/docker.sock jenkins [OK]

Hint: Mount socket with same host and container path [OK]

Common Mistakes:

• Swapping host and container paths
• Using incorrect socket path inside container
• Missing /var/run prefix

3. Given this Jenkins Docker run command:

docker run -d -v /var/run/docker.sock:/var/run/docker.sock jenkins

What will happen if Jenkins tries to run docker ps inside its container?

medium

A. It will show an error: Docker command not found

B. It will list running Docker containers on the host

C. It will list containers inside the Jenkins container only

D. It will fail because Docker daemon is not running inside Jenkins

Solution

1. Step 1: Understand socket mount effect

   Mounting the Docker socket lets Jenkins use the host's Docker daemon, so commands like docker ps run inside Jenkins actually query the host Docker.

2. Step 2: Predict command output

   Therefore, docker ps inside Jenkins will list containers running on the host, not inside Jenkins container.

3. Final Answer:

   It will list running Docker containers on the host -> Option B

4. Quick Check:

   Docker socket mount = host Docker commands inside container [OK]

Hint: Docker socket mount = host Docker commands work inside container [OK]

Common Mistakes:

• Thinking Docker runs inside Jenkins container
• Assuming Docker command is missing
• Confusing container vs host Docker context

4. You mounted the Docker socket in Jenkins container but get permission denied errors when running Docker commands inside Jenkins. What is the likely cause?

medium

A. Jenkins user inside container lacks permission to access the socket

B. Docker daemon is not installed on the host

C. The socket path inside container is incorrect

D. Jenkins container network is disconnected

Solution

1. Step 1: Analyze permission error cause

   The Docker socket file on the host has restricted permissions. If Jenkins runs as a user without access rights, it will get permission denied.

2. Step 2: Confirm other options

   Docker daemon must be running on host (else other errors). Socket path is correct if mounted. Network issues don't cause permission denied on socket.

3. Final Answer:

   Jenkins user inside container lacks permission to access the socket -> Option A

4. Quick Check:

   Permission denied = user lacks socket access [OK]

Hint: Check Jenkins user permissions on Docker socket [OK]

Common Mistakes:

• Blaming Docker daemon absence
• Assuming wrong socket path
• Confusing network issues with permissions

5. You want Jenkins to build Docker images inside its container using the host Docker engine. Which combination of steps is the safest and most effective approach?

hard

A. Mount /var/run/docker.sock and run Jenkins as root user inside container

B. Install Docker daemon inside Jenkins container and do not mount socket

C. Mount /var/run/docker.sock and add Jenkins user to Docker group on host and container

D. Use Docker-in-Docker (DinD) without mounting socket

Solution

1. Step 1: Understand mounting socket and permissions

   Mounting the Docker socket allows Jenkins to use host Docker. Running as root is risky and not recommended.

2. Step 2: Apply best practice for permissions

   Adding Jenkins user to Docker group on host and container grants needed permissions safely without root.

3. Step 3: Evaluate alternatives

   Installing Docker daemon inside Jenkins container duplicates effort and complicates setup. DinD is more complex and less secure.

4. Final Answer:

   Mount /var/run/docker.sock and add Jenkins user to Docker group on host and container -> Option C

5. Quick Check:

   Socket mount + Docker group permissions = safe Jenkins Docker use [OK]

Hint: Use socket mount + Docker group permissions, avoid root [OK]

Common Mistakes:

• Running Jenkins as root inside container
• Installing Docker daemon inside Jenkins container
• Using DinD without understanding risks