Docker engine and runtime - Step-by-Step Execution

Process Flow - Docker engine and runtime

User runs docker command

↓

Docker CLI sends request

↓

Docker Engine receives request

↓

Docker Engine communicates with Runtime

↓

Runtime creates/starts container

↓

Container runs isolated process

↓

Docker Engine monitors container

↓

User gets output or status

The Docker CLI sends commands to the Docker Engine, which uses the runtime to create and manage containers running isolated processes.

Execution Sample

Docker

docker run --name myapp alpine echo Hello

Runs a container named 'myapp' from the Alpine image that prints 'Hello' and then stops.

Process Table

Step	Action	Component	Result	Notes
1	User runs 'docker run --name myapp alpine echo Hello'	Docker CLI	Command sent to Docker Engine	CLI parses command and sends request
2	Docker Engine receives command	Docker Engine	Validates image 'alpine'	Checks local cache or pulls image
3	Docker Engine requests Runtime to create container	Docker Engine -> Runtime	Container 'myapp' created	Runtime sets up container environment
4	Runtime starts container process	Runtime	Runs 'echo Hello' inside container	Process runs isolated from host
5	Container outputs 'Hello'	Container process	Output sent to Docker Engine	Output captured by Docker Engine
6	Docker Engine sends output to CLI	Docker Engine -> CLI	User sees 'Hello'	Command completes
7	Container stops after command finishes	Runtime	Container 'myapp' exits	Container lifecycle ends
8	Docker Engine updates container status	Docker Engine	Container marked as stopped	Ready for inspection or removal

💡 Container process finishes, container stops, and Docker Engine updates status

Status Tracker

Variable	Start	After Step 3	After Step 4	After Step 7	Final
Container State	none	created	running	exited	exited
Process Output	none	none	Hello	Hello	Hello
Image Availability	may need pull	available	available	available	available

Key Moments - 3 Insights

Why does the container stop after printing 'Hello'?

Because the container runs the command 'echo Hello' which finishes immediately, so the runtime stops the container process as shown in execution_table step 7.

What role does the Docker Engine play between CLI and runtime?

Docker Engine acts as the middleman: it receives commands from CLI, manages images, and instructs the runtime to create and run containers, as seen in steps 2 and 3.

How does the output 'Hello' reach the user?

The container process outputs 'Hello', Docker Engine captures it, then sends it back to CLI to display to the user, shown in steps 5 and 6.

Visual Quiz - 3 Questions

Look at the execution table, at which step does the container start running?

A Step 4

B Step 5

C Step 3

D Step 7

💡 Hint

Check the 'Action' and 'Result' columns for when the container process begins.

According to the variable tracker, what is the container state after step 7?

A created

B running

C exited

D none

💡 Hint

Look at the 'Container State' row under 'After Step 7' in variable_tracker.

If the image 'alpine' was not available locally, which step would change?

A Step 1

B Step 2

C Step 3

D Step 5

💡 Hint

Refer to the 'Notes' in step 2 about image validation and pulling.

Concept Snapshot

Docker Engine receives commands from CLI
It manages images and container lifecycle
Runtime creates and runs containers
Containers run isolated processes
Output flows back through Engine to CLI
Container stops when process ends

Full Transcript

When you run a docker command like 'docker run', the Docker CLI sends this command to the Docker Engine. The Engine checks if the image is available locally or pulls it if needed. Then it asks the runtime to create a container and start the process inside it. The container runs the command isolated from the host. The output from the container process is captured by the Engine and sent back to the CLI so you can see it. When the command finishes, the container stops and the Engine updates its status. This flow ensures containers run quickly and isolated, managed by the Docker Engine and runtime.

Practice

1. What is the primary role of the Docker engine in container management?

easy

A. It manages and controls containers on your system.

B. It builds the Linux kernel for container support.

C. It acts as a cloud service for container hosting.

D. It provides a graphical interface for container design.

Solution

1. Step 1: Understand Docker engine's function

   The Docker engine is the main software that manages containers, including building, running, and controlling them.

2. Step 2: Compare options with this role

   Only It manages and controls containers on your system. correctly states that Docker engine manages and controls containers on your system.

3. Final Answer:

   It manages and controls containers on your system. -> Option A

4. Quick Check:

   Docker engine = container management [OK]

Hint: Docker engine controls containers, not builds kernels or UI [OK]

Common Mistakes:

• Confusing Docker engine with cloud services
• Thinking Docker engine builds the OS kernel
• Assuming Docker engine is a GUI tool

2. Which of the following is the correct command to check the Docker engine version?

easy

A. docker version

B. docker check-version

C. docker show version

D. docker engine info

Solution

1. Step 1: Recall Docker command syntax for version

   The correct command to check Docker engine version is docker version.

2. Step 2: Validate other options

   Options A, B, and C are not valid Docker commands for checking version.

3. Final Answer:

   docker version -> Option A

4. Quick Check:

   Check version command = docker version [OK]

Hint: Use 'docker version' to see engine version quickly [OK]

Common Mistakes:

• Using incorrect command names like 'docker check-version'
• Confusing 'docker info' with version command
• Trying 'docker engine info' which is invalid

3. What will be the output of the command docker ps when no containers are running?

medium

A. Displays an error saying no containers found

B. Lists all containers including stopped ones

C. Shows an empty list with only headers

D. Starts a new container automatically

Solution

1. Step 1: Understand what 'docker ps' shows

   The command docker ps lists running containers only, showing headers even if none are running.

2. Step 2: Analyze output when no containers run

   When no containers run, it shows an empty list with column headers but no container entries.

3. Final Answer:

   Shows an empty list with only headers -> Option C

4. Quick Check:

   docker ps with no containers = empty list [OK]

Hint: 'docker ps' shows running containers; empty if none run [OK]

Common Mistakes:

• Thinking it lists stopped containers too
• Expecting an error message when no containers run
• Assuming it starts containers automatically

4. You run docker run -d nginx but get an error: "Cannot connect to the Docker daemon." What is the likely cause?

medium

A. The container is already running.

B. The nginx image does not exist on Docker Hub.

C. The command syntax is incorrect.

D. Docker daemon is not running on the system.

Solution

1. Step 1: Understand the error message

   "Cannot connect to the Docker daemon" means the Docker engine service (daemon) is not running or accessible.

2. Step 2: Check other options

   Image absence or syntax errors cause different errors; container running does not cause daemon connection errors.

3. Final Answer:

   Docker daemon is not running on the system. -> Option D

4. Quick Check:

   Daemon connection error = daemon not running [OK]

Hint: Daemon errors mean Docker service is stopped or unreachable [OK]

Common Mistakes:

• Assuming image absence causes daemon errors
• Blaming command syntax for daemon connection issues
• Thinking container running causes this error

5. You want to run a container using a runtime other than the default Docker runtime. Which command option lets you specify the runtime?

hard

A. docker run --use-runtime=<runtime_name> <image>

B. docker run --runtime=<runtime_name> <image>

C. docker run --engine=<runtime_name> <image>

D. docker run --container-runtime=<runtime_name> <image>

Solution

1. Step 1: Recall Docker run options for runtime

   The correct option to specify a runtime is --runtime followed by the runtime name.

2. Step 2: Verify other options

   Options A, B, and D are not valid Docker CLI options for runtime selection.

3. Final Answer:

   docker run --runtime=<runtime_name> <image> -> Option B

4. Quick Check:

   Specify runtime with --runtime option [OK]

Hint: Use '--runtime' option to select container runtime [OK]

Common Mistakes:

• Using incorrect flags like --engine or --use-runtime
• Confusing runtime with engine options
• Omitting the runtime option entirely