What are Docker objects?

Docker Objects are the discrete entities or resources that the Docker Daemon manages. These are the building blocks of Docker.

1
Images: A read-only template with the instructions for creating a container. A snapshot of your app — like a recipe.
2
Containers: A runnable instance of an image. A live app built from the image — like a dish cooked from a recipe.
3
Volumes: Persistent storage used by containers to store data outside of the container’s filesystem. Think of it as a hard drive for containers — survives restarts or rebuilds.
4
Networks: Allow containers to communicate with each other and with the outside world. Docker creates a default bridge network, but you can define your own.
5
Plugins: Plugins allow you to extend Docker's capabilities. you might use a Storage Plugin to connect your containers directly to AWS EBS or an S3-backed filesystem, or a Logging Plugin to stream your Node.js logs directly to CloudWatch or ELK.

Difficulty: 4/10

Topics: containers, images, volumes

0-2 years experience

1
If you need to run a Python script in isolation, which Docker object would you create and what steps would you take?
2
What happens if you delete a Docker image that a running container is based on?
3
How would you persist data across container restarts using Docker objects?

2-5 years experience

1
Your CI pipeline is failing because a container can't find a volume you expected; how would you troubleshoot the Docker objects involved?
2
You need to ship a new version of an app without downtime; explain how you would use Docker images and containers to achieve a rolling update.
3
During a deployment you notice that two containers can't communicate; which Docker object would you examine and why?

5-8 years experience

1
Design a multi‑service application that requires shared configuration and persistent storage; which Docker objects would you choose and how would you orchestrate them for scalability?
2
Explain the trade‑offs of using bind mounts versus named volumes in a high‑throughput microservice architecture.
3
Your team is moving from Docker Compose to Kubernetes; how would you map Docker objects (containers, images, networks, volumes) to Kubernetes resources, and what challenges might arise?

8+ years experience

1
At a large enterprise you need to standardize Docker object naming, tagging, and lifecycle policies across dozens of teams; how would you design a governance model that balances flexibility and security?
2
When migrating legacy monolithic workloads to containerized services, what considerations around Docker images, layers, and storage drivers affect performance and compliance?
3
Propose a strategy for handling secret management and network isolation across multiple Docker Swarm clusters in different regions, focusing on the role of Docker objects.

❓How do you decide when to use a volume versus a bind mount?
❓What steps would you take to clean up unused Docker objects in a production environment?
❓Can you describe a time when an image layer caused an unexpected issue?