Docker agents for isolation in Jenkins - Step-by-Step Execution

Process Flow - Docker agents for isolation

Jenkins Master

↓

Request Build

↓

Allocate Docker Agent

↓

Start Docker Container

↓

Run Build Inside Container

↓

Build Complete

↓

Stop and Remove Container

↓

Return Results to Master

Jenkins master requests a build, allocates a Docker container as an isolated agent, runs the build inside it, then cleans up the container after completion.

Execution Sample

Jenkins

pipeline {
  agent {
    docker {
      image 'python:3.12'
    }
  }
  stages {
    stage('Build') { steps { sh 'python --version' } }
  }
}

This Jenkins pipeline runs the build inside a Docker container using the python:3.12 image for isolation.

Process Table

Step	Action	Docker Container State	Build Command	Output
1	Jenkins master starts pipeline	No container	N/A	N/A
2	Allocate Docker agent	Container created (python:3.12)	N/A	Container starting
3	Run build command inside container	Container running	python --version	Python 3.12.x
4	Build completes	Container running	N/A	Build success
5	Stop and remove container	Container stopped and removed	N/A	Cleanup done

💡 Build finished and container cleaned up to keep environment isolated

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 5
Docker Container	None	Created (python:3.12)	Running	Removed
Build Output	None	None	Python 3.12.x	Finalized

Key Moments - 2 Insights

Why does Jenkins create a new Docker container for each build?

Each build runs in a fresh container to keep environments clean and isolated, as shown in execution_table steps 2 and 5 where container is created and then removed.

What happens if the build command fails inside the Docker container?

The container still stops and is removed after the build attempt, ensuring no leftover state, similar to step 5 in the execution_table.

Visual Quiz - 3 Questions

Look at the execution table, what is the Docker container state at step 3?

A Container running

B No container

C Container stopped

D Container removed

💡 Hint

Refer to the 'Docker Container State' column at step 3 in the execution_table

At which step does Jenkins remove the Docker container?

A Step 2

B Step 5

C Step 3

D Step 4

💡 Hint

Check the 'Docker Container State' column for when the container is stopped and removed

If the build command was changed to 'python --help', how would the output in step 3 change?

A Output would show Python version

B Output would be empty

C Output would show Python help text

D Build would fail immediately

💡 Hint

Look at the 'Build Command' and 'Output' columns in step 3 to understand command-output relation

Concept Snapshot

Jenkins Docker agents run builds inside isolated containers.
Syntax: agent { docker { image 'image_name' } }
Each build gets a fresh container.
Build runs inside container, then container is removed.
Keeps builds clean and reproducible.

Full Transcript

This visual execution shows how Jenkins uses Docker agents for isolation. The Jenkins master starts a pipeline and requests a Docker agent. A new container is created from the specified image (python:3.12). The build command runs inside this container, producing output like the Python version. After the build finishes, Jenkins stops and removes the container to keep the environment clean. Variables like the Docker container state and build output change step-by-step. Key points include why containers are created fresh for each build and that containers are always cleaned up even if builds fail. The quiz tests understanding of container states and command outputs during the process.