Comment 2 for bug 1997139

Hi folks,

Quick 2024 update, for those who stumble on this bug report. This issue still persists on Ubuntu Jammy, and is not isolated only on `podman exec`. It also affects containers that have started with `podman run` and simply write lots of data in their standard streams [1]. Note that the Podman option `--log-driver none` does not help here, unfortunately.

The conmon version (2.0.25+ds1-1.1) that the original poster mentioned has not been updated yet. There is however a development on the Debian Bullseye side, which has a patched conmon (2.0.25+ds1-1.1+deb11u1) in the oldstable-proposed-updates repo [2], and will be shipped as part of the 11.9 release on February 10th [3].

Since Ubuntu Jammy will have it's next point release on February 22nd [4], can the maintainers backport the patch from Debian [5] and ship a new conmon version?

Cheers,
Alex

[1]: https://github.com/freedomofpress/dangerzone/issues/685
[2]: https://tracker.debian.org/news/1477995/accepted-conmon-2025ds1-11deb11u1-source-into-oldstable-proposed-updates/
[3]: https://lists.debian.org/debian-release/2024/01/msg00400.html
[4]: https://launchpad.net/ubuntu/+milestone/ubuntu-22.04.4
[5]: The patch is pretty trivial, it's basically a line removal: https://github.com/containers/conmon/commit/2b873145a85a212f703c9c00db13717ab0204318