Challenge - 5 Problems
Docker Engine Mastery
Get all challenges correct to earn this badge!
Test your skills under time pressure!
💻 Command Output
intermediate1:30remaining
Identify Docker Engine Version Output
What is the output of the command
docker version --format '{{.Server.Version}}' when Docker Engine version 24.0.2 is installed?Docker
docker version --format '{{.Server.Version}}'
Attempts:
2 left
💡 Hint
The --format option outputs only the specified field without extra text.
✗ Incorrect
The command outputs only the server version string exactly as '24.0.2' without any prefix or label.
🧠 Conceptual
intermediate1:30remaining
Docker Runtime Default Behavior
Which statement correctly describes the default runtime used by Docker Engine when running containers?
Attempts:
2 left
💡 Hint
Think about the low-level runtime that Docker calls to create containers.
✗ Incorrect
Docker Engine uses runc as the default runtime to create and run containers. containerd is a daemon Docker uses internally, but runc is the runtime that actually runs containers.
❓ Troubleshoot
advanced2:00remaining
Diagnose Docker Engine Startup Failure
A user reports that Docker Engine fails to start with the error message:
failed to start daemon: Error initializing network controller: Error creating default "bridge" network: failed to allocate gateway (172.17.0.1): Address already in use. What is the most likely cause?Attempts:
2 left
💡 Hint
The error mentions 'Address already in use' for the gateway IP.
✗ Incorrect
The error indicates the default Docker bridge network IP range overlaps with an existing network on the host, causing a conflict.
🔀 Workflow
advanced2:30remaining
Sequence to Change Docker Runtime
What is the correct sequence of steps to change the default Docker runtime from
runc to nvidia runtime on a Linux host?Attempts:
2 left
💡 Hint
Configuration changes require daemon restart before verification.
✗ Incorrect
First, configure the daemon.json file, then restart Docker to apply changes, verify the runtime is listed, and finally run containers using the new runtime.
✅ Best Practice
expert3:00remaining
Best Practice for Docker Engine Security Hardening
Which of the following is the best practice to minimize security risks when running Docker Engine in production?
Attempts:
2 left
💡 Hint
Think about isolating container privileges from the host system.
✗ Incorrect
Using user namespaces maps container root users to non-root users on the host, reducing risk if a container is compromised.