How To Use Docker Logs to Debug Containers
The docker logs command is a key diagnostic tool that outputs everything a container writes to standard output (stdout) and standard error (stderr). Whether you're troubleshooting failed startups, inspecting runtime behavior, or reviewing error traces, this command offers a direct view into container activity without needing to attach or exec into it.
While docker logs is ideal for capturing application output, it works best alongside tools like docker inspect and docker exec, which provide metadata and interactive shell access, respectively. This article explains how to use docker logs to inspect, stream, and filter logs so you can pinpoint and resolve issues efficiently.
The Short Answer Version
If you're already familiar with Docker and need a quick reference for checking container logs, use the commands below:
These commands cover the most common use cases for viewing and filtering logs. Continue reading for in-depth explanations and usage examples.
View Container Logs
Use the docker logs command to view output from a container’s standard output (stdout) and standard error (stderr). This includes application logs, startup messages, and error details, essential for diagnosing issues.
Command Syntax
docker logs: Displays the container's complete stdout and stderr output.<container_id>: The container’s short or full ID. Rundocker container lsto find it.
Use Case
- Displays all logs from the container since it started.
- Does not interrupt or modify the container’s running state.
- Useful for checking if services initialized correctly, troubleshooting startup issues, or inspecting runtime errors.
Command Demonstration
List the currently running containers.
CONSOLEOutput.
View the container logs using its ID or name.
CONSOLEOutput.
Stream Logs in Real Time
To monitor a running container continuously, use the -f or --follow flag with the docker logs command. This streams log output in real time and is useful when debugging live services or checking active processes.
Command Syntax
docker logs: Outputs all logs from the container's stdout and stderr.-for--follow: Continuously streams new log entries as they appear.<container_id>: The container’s short or full ID.
Use Case
- Streams live logs from both stdout and stderr.
- Keeps the terminal session open until you manually stop it with Ctrl + C.
- Useful for monitoring background jobs, web requests, or live deployment behavior.
Use this flag when observing a container's real-time performance or verifying live system responses.
Command Demonstration
List running containers.
CONSOLEStream logs from a selected container.
CONSOLEThis streams logs from the container in real time. Replace 8f8f72f26159 with your container ID. To stop, press Ctrl + C.
Filter Logs by Time and Lines
Docker allows you to filter container logs using specific flags. These filters help reduce log clutter, narrow down events within a time window, or extract only the most relevant entries during debugging.
The following flags control how much log data is shown and how it's displayed:
Each of these flags can be combined with docker logs to help you pinpoint issues more efficiently. The following sections explain their syntax and use cases with examples.
Show Recent Log Lines with --tail
Command Syntax
docker logs: Displays logs from the container’s stdout and stderr.--tail <number_of_lines>: Limits output to the last n lines. Accepts values like10,100, or500.<container_id>: The container’s short or full ID (usedocker container lsto find it).
Use Case
- Shows only the most recent lines from a container’s logs.
- Reduces output clutter when debugging recent activity.
- Useful when you want to avoid scrolling through long logs.
Command Demonstration
List running containers to find the container ID.
CONSOLEView the last 10 lines of logs from the container.
CONSOLEOutput.
View Logs From a Specific Time with --since
Command Syntax
docker logs: Displays logs from the container’s stdout and stderr.--since="<timestamp>": Filters log entries from the specified time onward. Accepts absolute timestamps like2025-05-20T10:00:00or relative formats like30m,2h, or1d.<container_id>: The container’s short or full ID.
Use Case
- Filters log output to show only entries created after a specific point in time.
- Helps isolate logs from a known window. Useful during debugging or testing.
- Supports both relative and ISO 8601 timestamp formats.
Use this flag when you're troubleshooting specific time-based events or testing application behavior within a known timeframe.
Command Demonstration
List running containers.
CONSOLEView logs generated after a specific timestamp.
CONSOLEThis command displays logs from container
ea45fa0f96acstarting at the given date and time.View logs from the last 30 minutes.
CONSOLEThis filters output to just the most recent 30 minutes of activity.
View Logs Until a Specific Time with --until
Command Syntax
docker logs: Displays logs captured from the container's stdout and stderr.--until="<timestamp>": Filters logs to show entries created before a specified time. Accepts absolute timestamps like2025-05-20T12:00:00or relative values like30mor2h.<container_id>: The container’s short or full ID.
Use Case
- Limits log output to entries created before a specific point in time.
- Helps identify what happened prior to a known issue or event.
- Works well with
--sinceto define a custom time window.
Use this flag to isolate logs that occurred before an application error, crash, or deployment.
Command Demonstration
List running containers.
CONSOLEIdentify the container ID you want to inspect.
To view logs created before a specific time (e.g., May 28, 2025, at 8:44:39 p.m.).
CONSOLEOutput.
To show logs generated more than two hours ago.
CONSOLE
This flag is especially useful when reviewing logs leading up to a failure window or diagnosing events that happened earlier in the day.
Add Timestamps to Logs with --timestamps
Command Syntax
docker logs: Displays logs from the container's stdout and stderr.--timestamps: Adds a timestamp to the beginning of each log line.<container_id>: The container’s short or full ID.
Use Case
- Appends ISO 8601 timestamps to each log entry.
- Helps correlate log events with application behavior and incident timelines.
- Useful for debugging time-sensitive issues.
Use this flag to track when log entries occur, especially during performance bottlenecks or request timing analysis.
Command Demonstration
Identify the container to inspect.
CONSOLEDisplay logs with timestamps.
CONSOLEOutput.
This flag is especially helpful when working with log aggregators or correlating logs across services.
Handle Errors When Viewing Logs
Running docker logs can sometimes result in errors such as:
or
These usually occur due to referencing the wrong container or lacking proper permissions. Use the following solutions to resolve these issues.
"No such container" Error
This error appears if the container ID or name is incorrect, incomplete, or the container has already stopped.
How to Fix It
List running containers.
CONSOLEIf the container isn’t running, include stopped containers.
CONSOLEUse the correct container name or full ID.
CONSOLE
Permission Denied Error
This typically happens when the current user does not have access to the Docker daemon.
How to Fix It
Use
sudoto run the command.CONSOLETo avoid using
sudoeach time, add your user to thedockergroup.CONSOLEThen log out and back in for the group change to take effect.
Conclusion
This article showed you how to use the docker logs command to debug containers effectively. You learned how to view logs from a running container, stream real-time output, and filter log data using flags like --tail, --since, --until, and --timestamps. You also reviewed how to fix common errors related to invalid container IDs or permission issues. These techniques help you diagnose problems faster and maintain stable Docker environments. For more details, see the official Docker logs documentation.
Tags:Docker
0 Comments
Be the first to comment and share your perspective with the community.