This set builds vocabulary for managing containers, volumes, and multi-service stacks locally.
0 / 5 completed
1 / 5
At standup, a dev mentions a GUI application on their laptop that manages a local container runtime, letting them run and inspect containers without a remote server. What is this tool called?
Docker Desktop provides a local container runtime and a graphical interface for managing containers, images, and volumes directly on a developer's own machine, without needing a remote server for local development and testing. This makes it possible to build and run the same containerized workloads locally that will eventually run in production. It's a common entry point for developers first working with containerization.
2 / 5
During a design review, the team wants to mount a local project directory into a running container so code changes are reflected immediately without rebuilding the image. Which capability supports this?
A bind mount maps a local directory on the host machine directly into a running container's filesystem, so edits made on the host are immediately visible inside the container without needing to rebuild the image each time. This dramatically speeds up the local development feedback loop compared to rebuilding after every change. It's a standard technique for live-reloading development workflows inside containers.
3 / 5
In a code review, a dev notices multiple related services, like a web app and its database, are defined together and started with one command. What does this represent?
A multi-container application defined via Compose declares several related services, like a web app and its database, in one configuration file so they can all be started, networked together, and stopped with a single command. This coordination avoids manually starting and wiring up each container's networking by hand. It's the standard way to model a local development stack with multiple interdependent services.
4 / 5
An incident report style retro shows a developer's laptop ran out of disk space because unused container images and volumes accumulated over months with no cleanup. What practice would prevent this?
Periodically pruning unused images, stopped containers, and orphaned volumes prevents them from silently accumulating and consuming significant local disk space over months of regular use. Never cleaning these up is exactly how a laptop can unexpectedly run out of storage. This maintenance habit is a routine part of working with a local container runtime over an extended period.
5 / 5
During a PR review, a teammate asks why the team develops locally against containers instead of installing each service's dependencies directly on their host machine. What is the reasoning?
Installing dependencies directly on a host machine risks version conflicts between different projects and drifting from how the application actually runs in production, while a container provides an isolated, reproducible environment much closer to that production setup. This closer parity reduces the risk of environment-specific bugs slipping through local testing. The tradeoff is the added resource overhead and learning curve of working with containers locally.