Why debugging containers matters in Docker - Why It Works

Introduction

Sometimes containers don't work as expected. Debugging containers helps find and fix problems inside them so your apps run smoothly.

When your containerized app crashes or stops unexpectedly

When a containerized service is slow or not responding

When you want to check logs or processes inside a running container

When you need to test changes inside a container without rebuilding it

When you want to understand why a container fails to start

Commands

This command lists all running containers so you can find the container ID or name to debug.

Terminal

docker ps

Expected Output

CONTAINER ID   IMAGE          COMMAND                  CREATED          STATUS          PORTS                    NAMES

b1c2d3e4f5g6   nginx:1.23.3   "/docker-entrypoint.…"   10 minutes ago   Up 10 minutes   0.0.0.0:8080->80/tcp     my-nginx

This shows the logs from the container named 'my-nginx' to help find error messages or clues about what is wrong.

Terminal

docker logs my-nginx

Expected Output

2024/06/01 12:00:00 [notice] 1#1: start worker process 10

2024/06/01 12:00:00 [notice] 1#1: signal process started

This opens an interactive shell inside the running container so you can run commands and inspect files directly.

Terminal

docker exec -it my-nginx sh

Expected Output

/ # 

→

-i - Keep STDIN open for interactive use

→

-t - Allocate a pseudo-TTY for the shell

Inside the container shell, this command lists running processes to check if your app or service is running properly.

Terminal

ps aux

Expected Output

PID   USER     TIME  COMMAND

1     root     0:00  nginx: master process nginx -g daemon off;

10    root     0:00  nginx: worker process

Exit the container shell and return to your host terminal after finishing debugging.

Terminal

exit

Expected Output

No output (command runs silently)

Key Concept

If you remember nothing else from this pattern, remember: debugging containers means looking inside them using logs and shells to find and fix problems.

Common Mistakes

Trying to debug without checking container logs first

Logs often contain the easiest clues about what went wrong, skipping them wastes time.

Always check container logs with 'docker logs' before deeper debugging.

Not using interactive shell to inspect container state

Without shell access, you cannot run commands or check files inside the container.

Use 'docker exec -it <container> sh' to open a shell inside the container.

Exiting the shell without saving findings or fixing issues

You lose the chance to understand or fix the problem if you leave too soon.

Take notes or fix issues inside the container before exiting.

Summary

Use 'docker ps' to find running containers to debug.

Check container logs with 'docker logs' to find error messages.

Open an interactive shell inside the container with 'docker exec -it' to inspect and fix problems.

Use commands like 'ps aux' inside the container to check running processes.

Exit the shell when done debugging.