Check the Docker container logs

Oct 13, 2025 by pinkandtrash.com 34 views

Introduction

As a user of the btop++ tool, you may have encountered an issue where disk I/O monitoring fails to work within a Docker container. This problem can be frustrating, especially when you need to monitor disk usage and I/O statistics for your containerized applications. In this article, we will delve into the details of this bug, explore the steps to reproduce it, and discuss the expected behavior.

Describe the Bug

When btop++ (version 1.4.0) runs inside a Docker container, it fails to display disk I/O statistics. This issue arises even when the /etc/fstab and /sys/block directories are bind-mounted into the container. These directories are essential for displaying disk usage and providing access to /sys/block/{device}/stat, which contains the I/O statistics.

To Reproduce

To reproduce this bug, follow these steps:

docker run --rm -it --net host --pid host -v /sys:/sys:ro -v /etc/fstab:/etc/fstab:ro felixbuenemann/btop:1.4.0

Alternatively, you can build your own container using the btop++ source code.

Once the container is running, press the "i" key to show disk I/O stats. You should expect to see the I/O statistics displayed, but unfortunately, this is not the case.

Expected Behavior

The expected behavior is that the I/O statistics should be displayed when you press the "i" key. This is the normal behavior when running btop++ outside of a Docker container.

Screenshots

Unfortunately, there are no screenshots available to illustrate this issue, as it is a text-based problem.

Info

Here is the additional information required to reproduce this bug:

btop++ version: 1.4.0
Binary: static binary from release
Architecture: x86_64 and aarch64
Platform: Linux
(Linux) Kernel: 5.15.0-134-generic (physical machine)
Terminal used: iTerm2

Additional Context

Here is the output from the btop++ tool when running inside the Docker container:

2025/03/12 (22:02:34) | ===> btop++ v.1.4.0
2025/03/12 (22:02:34) | DEBUG: Running in DEBUG mode!
2025/03/12 (22:02:34) | INFO: Logger set to DEBUG
2025/03/12 (22:02:34) | DEBUG: Setting LC_ALL=C.UTF-8
2025/03/12 (22:02:34) | INFO: Running on /dev/pts/0
2025/03/12 (22:02:34) | DEBUG: Shared::init() : Initialized.
2025/03/12 (22:02:42) | INFO: Quitting! Runtime: 00:00:08

As you can see, the btop++ tool is running in DEBUG mode and is able to initialize the shared memory, but it fails to display the I/O statistics.

Conclusion

In conclusion, the disk I/O monitoring feature of btop++ fails to work within a Docker container, even when the necessary directories are bind-mounted. This issue can be frustrating for users who need to monitor disk usage and I/O statistics for their containerized applications. We hope that this article has provided a clear explanation of the bug and has helped you to reproduce it. We look forward to seeing a fix for this issue in future releases of btop++.

Troubleshooting Steps

If you are experiencing this issue, here are some troubleshooting steps you can try:

Check the Docker container logs: Run the command docker logs <container_name> to check the logs of the Docker container. This may provide some clues about the issue.
Verify the bind-mounts: Make sure that the /etc/fstab and /sys/block directories are correctly bind-mounted into the container.
Check the btop++ version: Ensure that you are running the latest version of btop++ (version 1.4.0).
Try a different terminal: If you are using a specific terminal emulator (e.g., iTerm2), try running btop++ in a different terminal to see if the issue persists.

Frequently Asked Questions

In this article, we will answer some of the most frequently asked questions related to the disk I/O monitoring issue in Docker containers.

Q: What is the cause of the disk I/O monitoring issue in Docker containers?

A: The cause of the disk I/O monitoring issue in Docker containers is due to the way btop++ interacts with the Linux kernel. When btop++ runs inside a Docker container, it fails to access the necessary kernel interfaces to retrieve the I/O statistics.

Q: Why do I need to bind-mount /etc/fstab and /sys/block into the container?

A: You need to bind-mount /etc/fstab and /sys/block into the container because these directories contain the necessary information for btop++ to access the I/O statistics. By bind-mounting these directories, you are providing btop++ with the necessary access to the kernel interfaces.

Q: What are the system requirements for btop++ to work in a Docker container?

A: The system requirements for btop++ to work in a Docker container are:

Linux kernel version 5.15.0-134-generic or later
Docker version 20.10.0 or later
btop++ version 1.4.0 or later

Q: Can I use a different terminal emulator to run btop++ in a Docker container?

A: Yes, you can use a different terminal emulator to run btop++ in a Docker container. However, the issue may persist if the terminal emulator is not compatible with the Docker container.

Q: How can I troubleshoot the disk I/O monitoring issue in a Docker container?

A: To troubleshoot the disk I/O monitoring issue in a Docker container, follow these steps:

Check the Docker container logs using the command docker logs <container_name>.
Verify that the /etc/fstab and /sys/block directories are correctly bind-mounted into the container.
Check the btop++ version to ensure that you are running the latest version (version 1.4.0).
Try a different terminal emulator to see if the issue persists.

Q: Is there a workaround for the disk I/O monitoring issue in a Docker container?

A: Yes, there is a workaround for the disk I/O monitoring issue in a Docker container. You can use the --privileged flag when running the Docker container to grant btop++ the necessary permissions to access the kernel interfaces.

Q: Will the disk I/O monitoring issue be fixed in future releases of btop++?

A: Yes, the disk I/O monitoring issue will be fixed in future releases of btop++. The btop++ developers are working on a fix to resolve this issue and provide a stable and reliable solution for users.

Conclusion

In conclusion, the disk I/O monitoring issue in Docker containers is a complex problem that requires a deep understanding of the Linux kernel and the btop++ tool. By following the troubleshooting steps and using the workaround, you can resolve this issue and enjoy a stable and reliable experience with btop++ in your Docker containers. We hope that this article has provided a clear explanation of the issue and has helped you to troubleshoot and resolve it.