Docker socket mounting in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to mount the Docker socket inside the Jenkins container.

Jenkins

docker run -d -v [1]:/var/run/docker.sock jenkins/jenkins

Drag options to blanks, or click blank then click option'

A/var/run/docker.sock:/var/run/docker.sock

B/var/run/docker.sock

C/docker.sock

D/var/run/docker

Attempts:

3 left

💡 Hint

Common Mistakes

Mounting only the path without the container path.

Using incorrect socket path.

Forgetting the colon separator.

The Docker socket on the host is mounted inside the container at the same path to allow Docker commands inside the container.

2fill in blank

medium

Complete the Docker Compose service to mount the Docker socket for Jenkins.

Jenkins

services:
  jenkins:
    image: jenkins/jenkins
    volumes:
      - [1]:/var/run/docker.sock

Drag options to blanks, or click blank then click option'

A/var/run/docker

B/docker.sock

C/var/run/docker.sock

D/var/run/docker.sock:/var/run/docker.sock

Attempts:

3 left

💡 Hint

Common Mistakes

Including container path twice.

Using incorrect host path.

Using relative paths.

In Docker Compose, the volume mount is specified as host_path:container_path. Here, the container path is already specified, so only the host path is needed.

3fill in blank

hard

Fix the error in the Docker run command to correctly mount the Docker socket.

Jenkins

docker run -d -v [1] jenkins/jenkins

Drag options to blanks, or click blank then click option'

A/var/run/docker.sock

B/var/run/docker.sock:/var/run/docker.sock

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

D/docker.sock:/var/run/docker.sock

Attempts:

3 left

💡 Hint

Common Mistakes

Using mismatched paths.

Omitting the container path.

Using incorrect socket path.

The volume mount must specify both host and container paths separated by a colon, and both paths must be the Docker socket path.

4fill in blank

hard

Fill both blanks to mount the Docker socket and set the correct environment variable for Jenkins.

Jenkins

docker run -d -v [1]:/var/run/docker.sock -e [2]=unix:///var/run/docker.sock jenkins/jenkins

Drag options to blanks, or click blank then click option'

A/var/run/docker.sock

BDOCKER_HOST

Cdocker.sock

DDOCKER_SOCKET

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong environment variable name.

Mounting incorrect socket path.

Confusing volume mount syntax.

The Docker socket must be mounted from the host path /var/run/docker.sock. The environment variable DOCKER_HOST tells Jenkins where to find the Docker daemon.

5fill in blank

hard

Fill all three blanks to create a Docker Compose service for Jenkins with Docker socket mounting and environment variable.

Jenkins

services:
  jenkins:
    image: jenkins/jenkins
    volumes:
      - [1]:/var/run/docker.sock
    environment:
      - [2]=[3]

Drag options to blanks, or click blank then click option'

A/var/run/docker.sock

BDOCKER_HOST

Cunix:///var/run/docker.sock

Ddocker.sock

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect volume mount syntax.

Wrong environment variable name or value.

Using relative paths instead of absolute.

The Docker socket is mounted from the host path. The environment variable DOCKER_HOST is set to the Docker daemon address.

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