podman exec session aborts when writing many output lines

Bug #1997139 reported by Benedikt Fein
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
conmon (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Noticed with conmon/jammy,now 2.0.25+ds1-1.1 amd64.

The `podman exec` command for a container aborts whenever many lines are written to stdout. This is common, e.g., when backing up a database running inside a container using `mysqldump`.

Issue in the podman repo: https://github.com/containers/podman/issues/9724
Comment with link to fix: https://github.com/containers/podman/issues/9724#issuecomment-1152602817

As reported in the comment, I can confirm that manually installing conmon v2.0.32 from source fixes the issue on my system.
```sh
apt install libsystemd-dev libglib2.0-dev libseccomp-dev

make
make podman # installs the conmon binary to /usr/local/libexec/podman/
```

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: conmon 2.0.25+ds1-1.1
ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
Uname: Linux 5.15.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sat Nov 19 08:47:41 2022
SourcePackage: conmon
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Benedikt Fein (bfein) wrote :
Revision history for this message
Alex Pyrgiotis (apyrgio) wrote :

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

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in conmon (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.