Docker socket mounting in Jenkins - Step-by-Step Execution

Process Flow - Docker socket mounting

Start Jenkins Container

↓

Mount /var/run/docker.sock

↓

Jenkins uses Docker CLI

↓

Docker commands sent to host Docker daemon

↓

Host Docker daemon executes commands

↓

Containers created/managed on host

↓

Jenkins monitors container status

Jenkins container mounts the Docker socket file from the host, allowing Jenkins to control Docker on the host directly.

Execution Sample

Jenkins

docker run -d \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v jenkins_home:/var/jenkins_home \
  jenkins/jenkins:lts

This command runs Jenkins container mounting the Docker socket so Jenkins can run Docker commands on the host.

Process Table

Step	Action	Mount Status	Docker Command Source	Docker Daemon Response	Result
1	Start Jenkins container	Socket not mounted yet	N/A	N/A	Jenkins container initializing
2	Mount /var/run/docker.sock	Socket mounted inside container	Jenkins container	Host Docker daemon ready	Jenkins can send Docker commands
3	Jenkins runs 'docker ps'	Socket mounted	Jenkins container	Host Docker daemon lists containers	Output: list of running containers
4	Jenkins runs 'docker run alpine'	Socket mounted	Jenkins container	Host Docker daemon creates alpine container	New container started on host
5	Jenkins monitors container status	Socket mounted	Jenkins container	Host Docker daemon reports status	Jenkins sees container running
6	Stop Jenkins container	Socket unmounted	N/A	N/A	Jenkins container stops, no Docker control

💡 Jenkins container stops or socket unmounted, Docker commands no longer forwarded

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
Socket Mounted	false	true	true	true	true	false
Docker Command Source	N/A	Jenkins container	Jenkins container	Jenkins container	Jenkins container	N/A
Containers on Host	existing containers	existing containers	existing containers	existing + alpine	existing + alpine	existing + alpine

Key Moments - 3 Insights

Why does Jenkins need the Docker socket mounted?

Mounting the Docker socket allows Jenkins inside the container to send commands directly to the host's Docker daemon, as shown in execution_table step 2 and 3.

What happens if the socket is not mounted?

Without the socket mounted, Jenkins cannot communicate with the host Docker daemon, so Docker commands fail or do nothing, as seen in step 1 where socket is not mounted.

Does mounting the socket give Jenkins full control over host Docker?

Yes, mounting the socket gives Jenkins the same Docker control as the host user, so it can create, stop, and manage containers, as shown in steps 4 and 5.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does Jenkins first successfully run a Docker command?

A Step 3

B Step 2

C Step 4

D Step 1

💡 Hint

Check the 'Docker Command Source' and 'Docker Daemon Response' columns in execution_table rows.

According to variable_tracker, what is the state of 'Socket Mounted' after step 5?

A N/A

B false

C true

D unknown

💡 Hint

Look at the 'Socket Mounted' row and the column 'After Step 5' in variable_tracker.

If the socket was not mounted, how would the 'Docker Command Source' column in execution_table change?

A It would show 'Host Docker daemon' instead of 'Jenkins container'

B It would remain 'Jenkins container' but commands would fail

C It would be 'N/A' for all steps

D It would show 'Jenkins container' and commands succeed

💡 Hint

Consider what happens when Jenkins tries to run Docker commands without socket mounting, referencing step 1 and 2.

Concept Snapshot

Docker socket mounting lets a container (like Jenkins) access the host's Docker daemon.
Mount /var/run/docker.sock from host to container.
This enables running Docker commands inside the container that affect host containers.
Without mounting, Docker commands inside container fail.
Use: docker run -v /var/run/docker.sock:/var/run/docker.sock ...

Full Transcript

Docker socket mounting means sharing the Docker daemon's communication file from the host into a container. When Jenkins runs inside a container, it cannot control Docker on the host unless it has access to the Docker socket file. By mounting /var/run/docker.sock from the host into the Jenkins container, Jenkins can send Docker commands directly to the host's Docker daemon. This allows Jenkins to create, list, and manage containers on the host as if it was running Docker commands locally. The execution steps show starting Jenkins without the socket (no Docker control), then mounting the socket, running Docker commands successfully, and finally stopping Jenkins which removes Docker control. Variables track the socket mount status and containers on the host. Key moments clarify why mounting is needed and the security implications. The quiz tests understanding of when Docker commands succeed and the effect of mounting the socket.