Docker Interview Questions - Medium Part 2

⇩ Download!

Priyansh Khodiyar

Author

Share with friends

More on the topic

Docker Books

Docker Interview Questions - Beginner Level

Docker Interview Questions - Medium Level Part 1

Docker Interview Questions - Medium Level Part 2

Docker Interview Questions - Advanced Level Part 1

Docker Interview Questions - Advanced Level Part 2

Docker Interview Questions - Advanced Level Part 3

Docker Interview Questions - Advanced Level Part 4

1. What is Docker and how does it differ from virtual machines?

Answer:

Docker is a platform used by developers to build, ship, and run applications inside containers. These containers are lightweight, portable, and efficient as they share the host system's operating system kernel.

Virtual Machines (VMs):

• Each VM runs its own full operating system, which means they are heavier and require more resources.
• VMs use a hypervisor to manage and allocate resources.

Containers:

• Containers share the host OS kernel, which makes them lightweight and fast.
• Docker containers can start up quickly, usually in seconds, compared to VMs which can take minutes.

Analogy: Imagine you have several houses (VMs) and each house has its own utilities (electricity, water, gas). On the other hand, think of containers as apartments in a single building sharing the same utilities. The apartments are quicker and cheaper to maintain because they share resources.

2. What is a Dockerfile and what is its purpose?

Answer:

A Dockerfile is a text document that contains a series of instructions on how to build a Docker image. It automates the process of creating Docker images, ensuring consistency and repeatability.

Example:

# Use an official Python runtime as a parent image
FROM python:3.8-slim

# Set the working directory in the container
WORKDIR /app

# Copy the current directory contents into the container
COPY . /app

# Install any needed packages specified in requirements.txt
RUN pip install --no-cache-dir -r requirements.txt

# Make port 80 available to the world outside this container
EXPOSE 80

# Define environment variable
ENV NAME World

# Run app.py when the container launches
CMD ["python", "app.py"]

Explanation:

• FROM: Specifies the base image to use (Python 3.8 in this case).
• WORKDIR: Sets the working directory inside the container.
• COPY: Copies files from the host to the container.
• RUN: Executes commands in the container (like installing dependencies).
• EXPOSE: Exposes a port.
• ENV: Sets environment variables.
• CMD: Specifies the command to run when the container starts.

3. How do you manage data in Docker? Explain volumes and bind mounts.

Answer:

In Docker, you manage data using volumes and bind mounts.

Volumes:

• Managed by Docker.
• Stored in a part of the host filesystem managed by Docker (/var/lib/docker/volumes/ on Linux).
• Best when you want Docker to handle the storage.

Bind Mounts:

• You control the exact location on the host.
• You can use any location on the host filesystem.
• Useful when you need to access host files and directories directly.

Example using Volumes:

docker run -d -v my-volume:/app/data my-container

Example using Bind Mounts:

docker run -d -v /path/on/host:/app/data my-container

Table Comparison:

4. What is the difference between the ADD and COPY commands in a Dockerfile?

Answer:

Both ADD and COPY are used to copy files from the host to the Docker image, but there are key differences:

COPY:

• Simplest and most commonly used.
• Copies files and directories from the host to the container.

ADD:

• More powerful and flexible.
• Can copy files and directories, but also has additional features:
• Can extract compressed files (like tar).
• Can copy files from a URL.

When to Use:

• Use COPY when you simply need to copy files and directories.
• Use ADD when you need to extract files or download files from a URL.

Example:

# Using COPY
COPY myfile.txt /app/

# Using ADD
ADD myfile.tar.gz /app/
ADD https://example.com/myfile.txt /app/

For simplicity and clarity, prefer COPY unless you specifically need the features of ADD.

5. Explain Docker networking. What are the different types of networks available?

Answer:

Docker networking allows containers to communicate with each other and with the outside world.

Types of Docker Networks:

1. Bridge Network:

• Default network for containers.
• Suitable for containers on a single host.
• Containers can communicate using IP addresses or container names.

2. Host Network:

• The container shares the host’s network stack.
• The container and the host aren't separated by a network.
• Useful for performance optimization and low-latency applications.

3. Overlay Network:

• Lets containers on separate Docker hosts chat with each other.
• Used in Docker Swarm and multi-host networking.
• Requires a key-value store like etcd or Consul.

4. Macvlan Network:

• Gives every container its own MAC address.
• Containers appear as physical devices on the network.
• Suitable for legacy applications requiring direct access to the physical network.

Example:

# Creating a bridge network
docker network create my-bridge-network

# Running containers on the bridge network
docker run -d --network my-bridge-network my-container

Analogy: Think of Docker networks like different types of roads:

• Bridge: Local streets within a neighborhood (single host).
• Host: Your driveway, directly connected to your house (host).
• Overlay: Highways connecting different cities (multi-host).
• Macvlan: Private driveways that look like public streets (physical network access).

6. How do you use Docker Compose?

Answer:

Docker Compose is a nifty tool that helps you set up and run Docker applications made up of multiple containers. You can use a file called docker-compose.yml to describe the different parts of your application and how they should work together.

Example docker-compose.yml:

version: '3'
services:
 web:
   image: nginx
   ports:
     - "80:80"
 database:
   image: postgres
   environment:
     POSTGRES_PASSWORD: example

Steps:

1. Define Services: Describe each service (web, database) in the docker-compose.yml file.
2. Run Services: Use the docker-compose command to start the services.

docker-compose up

Explanation:

• version: Specifies the version of the Compose file format.
• services: Lists the services (containers) to run.
• image: Specifies the Docker image to use.
• ports: Maps host ports to container ports.
• environment: Sets environment variables.

7. What are Docker Swarm and Kubernetes, and how do they compare?

Answer:

Docker Swarm:

• Docker's native clustering and orchestration tool.
• Allows you to manage a cluster of Docker nodes as a single virtual system.
• Easier to set up and use, tightly integrated with Docker.

Kubernetes:

• An open-source container orchestration platform.
• More powerful and flexible, but also more complex to set up.
• Widely adopted, with extensive community support and features.

Comparison:

Analogy: Think of Docker Swarm as a small, easy-to-drive car that gets you from point A to B with minimal fuss. Kubernetes is like a big, powerful truck that can handle any load and terrain but requires more skill to operate.

8. How do you troubleshoot a Docker container that is not starting?

Answer:

Steps to Troubleshoot:

1. Check Container Logs:

docker logs <container-id>

Look for error messages that explain why the container is not starting.

2. Inspect the Container:

docker inspect <container-id>

Check the container’s configuration and state for issues.

3. Check Resource Limits: Ensure the container has enough CPU and memory to start.

4. Check Dependencies: Ensure any required services or networks are available.

5. Run in Interactive Mode: Start the container with a shell to interactively debug.

docker run -it <image> /bin/sh

Example Scenario: If a web server container isn’t starting, check the logs:

docker logs my-web-server

If you see an error about a missing configuration file, ensure it’s correctly copied into the container:

docker inspect my-web-server

Check the Volumes section to verify the file paths.

9. Explain the concept of multi-stage builds in Docker.

Answer:

Multi-stage builds in Docker allow you to use multiple FROM statements in your Dockerfile to create more efficient and smaller images. You can separate the build environment from the final runtime environment.

Why Use Multi-Stage Builds?

• Reduces image size by copying only the necessary artifacts to the final image.
• Improves security by excluding unnecessary tools and dependencies from the final image.

Example:

# Stage 1: Build stage
FROM golang:1.16 as builder
WORKDIR /app
COPY . .
RUN go build -o myapp

# Stage 2: Final stage
FROM alpine:latest
WORKDIR /app
COPY --from=builder /app/myapp .
CMD ["./myapp"]

Explanation:

1. Stage 1 (Builder): Uses the Golang image to compile the application.
2. Stage 2 (Final): Uses a lightweight Alpine image to run the compiled application, copying only the necessary binary from the builder stage.

10. What is the purpose of the .dockerignore file?

Answer:

The .dockerignore file is like a bouncer for your Docker image. It decides which files and folders don't get to come along for the ride when you're building the image. This helps keep the image lean and mean, making the build process faster and ensuring that only the essential stuff makes it into the final product.

Example .dockerignore:

node_modules
*.log
.DS_Store

Explanation:

• node_modules: Excludes the node_modules directory to avoid copying dependencies into the image.
• *.log: Ignores all log files.
• .DS_Store: Ignores macOS system files.

Benefits:

• Reduces the image size by excluding unneeded files.
• Speeds up the build process by reducing the amount of data to transfer.

11. How do you use Docker to scale an application?

Answer:

To scale an application with Docker, you can use Docker Compose or Docker Swarm.

Using Docker Compose:

1. Define the number of replicas in the docker-compose.yml file.

version: '3'
services:
  web:
    image: nginx
    deploy:
      replicas: 3
    ports:
      - "80:80"

2. Run the following command to scale the services:

docker-compose up --scale web=3

Using Docker Swarm:

1. Initialize Docker Swarm:

docker swarm init

2. Create a service and scale it:

docker service create --name web --replicas 3 -p 80:80 nginx

Benefits of Scaling:

• Distributes the load across multiple containers.
• Increases application availability and fault tolerance.

12. How do you ensure data persistence in Docker containers?

Answer:

To ensure data persistence, you can use volumes or bind mounts.

Using Volumes:

• Volumes are managed by Docker and stored in a location determined by Docker.
• They persist data even if the container is removed.

Example:

docker run -d -v my-volume:/data my-container

Using Bind Mounts:

• Bind mounts map a directory on the host to a directory in the container.
• They provide direct access to host files.

Example:

docker run -d -v /path/on/host:/data my-container

Comparison:

13. What are Docker Tags and how are they used?

Answer:

Docker tags are used to identify different versions of Docker images. A tag is an alias attached to a specific image ID.

Example:

docker pull ubuntu:20.04
docker pull ubuntu:latest

In this example:

• 20.04 is a tag representing Ubuntu version 20.04.
• latest is a tag representing the latest version of Ubuntu.

Using Tags in a Dockerfile:

FROM nginx:1.19

Benefits of Tags:

• Version control: Easily manage different versions of an image.
• Stability: Pin to specific versions to avoid breaking changes from updates.

14. How do you handle environment variables in Docker?

Answer:

Environment variables can be passed to Docker containers in several ways:

1. Using the -e flag:

docker run -e MY_ENV_VAR=value my-container

2. Using an environment file: Create a file named .env:

MY_ENV_VAR=value

Pass the file when running the container:

docker run --env-file .env my-container

3. In a Dockerfile:

ENV MY_ENV_VAR value

Benefits:

• Configurable: Easily change configuration without modifying the image.
• Secure: Avoid hardcoding sensitive data in the image.

15. Explain the purpose of Docker Hub.

Answer:

Docker Hub is a cloud-based repository where Docker users can store and share their Docker images. It is the default public registry used by Docker.

Features:

• Public and Private Repositories: Store images publicly or privately.
• Automated Builds: Automatically build images from GitHub or Bitbucket repositories.
• Image Distribution: Easily share images with others.

Example: To pull an image from Docker Hub:

docker pull nginx

Benefits:

• Centralized storage: Easily access and share Docker images.
• Collaboration: Share images with team members or the community.
• Automation: Automate image builds and updates.

16. How do you update a running Docker container?

Answer:

To update a running Docker container, follow these steps:

1. Stop the Container:

docker stop my-container

2. Remove the Container:

docker rm my-container

3. Pull the Latest Image:

docker pull my-image:latest

4. Start a New Container:

docker run -d --name my-container my-image:latest

Explanation:

• Stopping and removing the container ensures there are no conflicts with the new version.
• Pulling the latest image gets the updated version.
• Starting a new container runs the updated version.

Alternative: Using Docker Compose: If using Docker Compose, you can update the services with:

docker-compose up -d

17. What is the docker exec command used for?

Answer:

The docker exec command allows you to run a command in a running container. It is useful for debugging and administrative tasks.

Example: To open a shell inside a running container:

docker exec -it my-container /bin/sh

Explanation:

• -i: Keep STDIN open.
• -t: Allocate a pseudo-TTY (terminal).

Use Cases:

• Debugging: Run diagnostic commands inside a container.
• Administration: Perform maintenance tasks without stopping the container.

18. What are the security best practices for Docker?

Answer:

Security Best Practices:

1. Use Official Images:

• Prefer images from official or trusted sources to reduce the risk of vulnerabilities.

2. Minimize Container Privileges:

• Make sure your containers don't have more permissions than they need.
• Don't run containers as the main administrator (root user).

3. Use Read-Only Filesystems:

• Set containers' filesystems to read-only to prevent unauthorized changes.

4. Update Regularly:

• Keep Docker and images up to date with the latest security patches.

5. Scan Images for Vulnerabilities:

• Use tools like Docker Bench for Security or image scanning services to detect vulnerabilities.

Example Commands:

• To run a container with a read-only filesystem:

docker run --read-only my-container

19. What is Docker Registry?

Answer:

Docker Registry: It's like a storage house and delivery service for Docker images. Docker Hub is the go-to public registry, but you can set up your own private one if you want.

Features:

• Store Images: Save and manage Docker images.
• Distribute Images: Share images between different environments (development, testing, production).
• Automated Builds: Automatically build and push images from source code repositories.

Example: To set up a private registry:

docker run -d -p 5000:5000 --name registry registry:2

Benefits:

• Control: Manage your own image repository.
• Security: Keep sensitive images private.
• Efficiency: Improve deployment speed by using a local registry.

20. How do you clean up unused Docker resources?

Answer:

To clean up unused Docker resources like images, containers, volumes, and networks, you can use the following commands:

1. Remove Unused Images:

docker image prune -a

2. Remove Stopped Containers:

docker container prune

3. Remove Unused Volumes:

docker volume prune

4. Remove Unused Networks:

docker network prune

5. Clean Up All at Once:

docker system prune -a

Explanation:

• These commands help reclaim disk space and keep your Docker environment tidy by removing resources that are no longer needed.

21. What is the difference between a Docker image and a Docker container?

Answer:

Docker Image: -In simple terms, a Docker image is like a neat little box that contains everything you need to run a software program. It's got the code, the runtime, libraries, environment variables, and configuration files all bundled up together.

• It is the blueprint or template from which Docker containers are created.
• Images are immutable and can be versioned.

Docker Container:

• A Docker container is a runnable instance of a Docker image. It is a lightweight, isolated environment that runs the software.
• Containers are created from images and can be started, stopped, moved, and deleted.
• Unlike images, containers have a writable layer that allows changes to the state of the container.

Analogy: Think of a Docker image as a recipe, while a Docker container is the actual dish prepared from that recipe. You can make multiple dishes (containers) from the same recipe (image).

22. Explain the docker-compose up and docker-compose down commands.

Answer:

docker-compose up:

• This command starts and runs all the services defined in the docker-compose.yml file.
• It builds images if they do not exist, creates containers, and starts the services.
• The -d flag runs the services in detached mode (in the background).

Example:

docker-compose up -d

docker-compose down:

• This command stops and removes all the containers, networks, and volumes created by docker-compose up.
• It ensures that the environment is cleaned up and resources are freed.

Example:

docker-compose down

23. How do you use Docker to run multiple services in a single container?

Answer:

Running multiple services in a single container is generally not recommended, as it goes against the principles of containerization. However, it can be done using process managers like supervisord or by running scripts to start all services.

Example Using supervisord:

1. Install supervisord:

FROM ubuntu:latest
RUN apt-get update && apt-get install -y supervisor

# Copy supervisord configuration file
COPY supervisord.conf /etc/supervisor/conf.d/supervisord.conf

CMD ["/usr/bin/supervisord"]

2. Create supervisord.conf:

[supervisord]
nodaemon=true

[program:service1]
command=/path/to/service1

[program:service2]
command=/path/to/service2

Explanation:

• supervisord is used to start and manage multiple services within a single container.
• The supervisord.conf file defines the services to run and their respective commands.

While possible, running multiple services in a single container is best avoided. Instead, use multiple containers with Docker Compose to manage dependencies and lifecycle more effectively.

24. What is the purpose of the ENTRYPOINT instruction in a Dockerfile?

Answer:

In a Dockerfile, the "ENTRYPOINT" command sets the default command that runs when you start a container. This lets you create a container that acts like a program when you run it.

Example:

FROM ubuntu:latest
ENTRYPOINT ["echo", "Hello, World!"]

Explanation:

• This Dockerfile will create a container that always runs the echo command with the argument "Hello, World!" when started.

Difference Between CMD and ENTRYPOINT:

• CMD: Provides default arguments for the ENTRYPOINT or specifies a command to run if no ENTRYPOINT is defined. Can be overridden at runtime.
• ENTRYPOINT: Defines the main command to run in the container. Cannot be easily overridden at runtime.

Use ENTRYPOINT when you want to define the primary behavior of the container, ensuring that the specified command always runs.

25. How do you handle logging in Docker?

Answer:

Docker provides several logging drivers to handle container logs. By default, it uses the json-file driver, which writes logs to a JSON file on the host.

Common Logging Drivers:

• json-file: Default logging driver, writes logs to JSON files.
• syslog: Sends logs to the syslog daemon on the host.
• journald: Uses the journald daemon for log management.
• fluentd: Sends logs to a Fluentd collector.
• awslogs: Sends logs to Amazon CloudWatch.

Example: To use the syslog logging driver:

docker run --log-driver=syslog my-container

Managing Logs with docker-compose:

version: '3'
services:
 web:
   image: nginx
   logging:
     driver: syslog

Next Steps

Docker Books

Docker Interview Questions - Beginner Level

Docker Interview Questions - Medium Level Part 1

Docker Interview Questions - Medium Level Part 2

Docker Interview Questions - Advanced Level Part 1

Docker Interview Questions - Advanced Level Part 2

Docker Interview Questions - Advanced Level Part 3

Docker Interview Questions - Advanced Level Part 4

Share with friends

Written by Priyansh Khodiyar

TwitterLinkedIn

Priyansh is the founder of UnYAML and a software engineer with a passion for writing. He has good experience with writing and working around DevOps tools and technologies, APMs, Kubernetes APIs, etc and loves to share his knowledge with others.