Monitoring Docker Log Sizes: Comprehensive Guide for 2026

Docker is an essential tool for developers, providing a consistent environment for application deployment. However, managing logs within Docker can be challenging. Large log files can quickly consume disk space, leading to performance issues. This guide will teach you how to list and manage Docker log sizes for all containers, ensuring optimal performance and efficient resource usage.

Key Takeaways

• Understand the importance of monitoring Docker log sizes to prevent disk space issues.
• Learn how to use Docker and Linux commands to check log sizes.
• Discover methods to clean up logs and manage disk usage effectively.
• Get tips on setting up automated log management to avoid manual checks.

Prerequisites

• Basic understanding of Docker and command-line interfaces.
• Docker installed on your system (version 24.0.0 or later).
• Access to a terminal with administrative privileges.

Step 1: Understanding Docker Logs

Docker stores logs in JSON format by default. These logs are essential for debugging and monitoring but can grow rapidly if not managed. Understanding where these logs reside and how they are stored is crucial for efficient management.

Step 2: Locate Docker Log Files

Docker log files are typically stored in the /var/lib/docker/containers/[container-id]/ directory. Each container has its own log file named [container-id]-json.log.

ls -lh /var/lib/docker/containers/*/*-json.log

This command lists the log files with their sizes, helping you identify containers with large log files.

Step 3: Check Log Sizes Using Docker Commands

While Docker’s command-line tools don’t directly show log sizes, you can use the following workaround to list all containers and their log sizes:

docker ps -q | xargs -I {} sh -c 'echo -n "{}: "; du -sh /var/lib/docker/containers/{}/{}-json.log'

This command lists each container ID followed by the size of its log file.

Step 4: Cleaning Up Logs

To manage disk usage, regularly clean up old logs. Docker provides a log rotation mechanism that you can configure in the Docker daemon settings.

{
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "10m",
    "max-file": "3"
  }
}

Place this configuration in your /etc/docker/daemon.json file and restart Docker with sudo systemctl restart docker.

Step 5: Automating Log Management

To avoid manual checks and cleanups, consider using automated tools like Logrotate, which can be configured to rotate and compress logs automatically.

/var/lib/docker/containers/*/*.log {
  rotate 5
  daily
  compress
  delaycompress
  missingok
  notifempty
  copytruncate
}

Add this configuration to a Logrotate file to manage your Docker logs effortlessly.

Common Errors/Troubleshooting

If you encounter permission errors, ensure that you have the necessary privileges to access Docker directories. Additionally, check Docker’s documentation for any version-specific changes in log management.

Frequently Asked Questions

How do I find the size of Docker logs?

You can list log files with their sizes using Linux commands in the Docker containers directory.

Can Docker automatically rotate logs?

Yes, Docker can automatically rotate logs by configuring the log driver options in the Docker daemon settings.

What happens if Docker logs fill up my disk?

Full disks can cause Docker and the host system to become unresponsive. Regular log management and cleanup are essential.

Frequently Asked Questions

How do I find the size of Docker logs?

You can list log files with their sizes using Linux commands in the Docker containers directory.

Can Docker automatically rotate logs?

Yes, Docker can automatically rotate logs by configuring the log driver options in the Docker daemon settings.

What happens if Docker logs fill up my disk?

Full disks can cause Docker and the host system to become unresponsive. Regular log management and cleanup are essential.