podman: podman exec into a "-it" container: container create failed (no logs from conmon): EOF

Common thread seems to be:

Running: podman [options] run -dti --name test1 quay.io/libpod/fedora-minimal:latest sleep +Inf
time="2021-06-16T19:33:53-05:00" level=warning msg="The input device is not a TTY. The --tty and --interactive flags might not work properly"
99e3b419a97aa408a4d0d3072bbd00579d5edd7c97790aa06d61f233cfdc1b4c
Running: podman [options] exec -ti test1 true
Running: podman [options] exec -ti test1 true       ! sometimes it fails on the first, sometimes on the third
Error: container create failed (no logs from conmon): EOF

Podman exec [It] podman exec terminal doesn’t hang

fedora-34 : int podman fedora-34 root container
- PR #10214
  - 05-05 10:20
fedora-34 : int podman fedora-34 root host
- PR #10860
- PR #10688
  - 06-16 20:43
gce_instance:fedora : int podman fedora-33 root host
- PR #9820
- PR #9477
instance:GCEInstance : int podman fedora-33 root host
- PR #9969
ubuntu-2104 : int podman ubuntu-2104 rootless host
- PR #10631
  - 06-10 04:18

And also just now in a still-live PR (my flake-xref does not handle live PRs): int podman ubuntu-2104 root host

Note: the March and April logs above have been garbagecollected, I can’t confirm that the error is the same one. I’m leaving them in the report deliberately, in case it helps to have a timestamp for the start of this flake (i.e. it might not be new in June).

Edit: this is podman, not podman-remote, so it’s unlikely to be the same as #7360

About this issue

Original URL
State: open
Created 3 years ago
Comments: 73 (20 by maintainers)

Commits related to this issue

readConmonPipeData: try to improve error Issue #10927 reports `container create failed (no logs from conmon): EOF` errors. Since we do not know the root cause it would be helpful to try to get as muc... — committed to Luap99/libpod by Luap99 2 years ago
readConmonPipeData: try to improve error Issue #10927 reports `container create failed (no logs from conmon): EOF` errors. Since we do not know the root cause it would be helpful to try to get as muc... — committed to Luap99/libpod by Luap99 2 years ago
readConmonPipeData: try to improve error Issue #10927 reports `container create failed (no logs from conmon): EOF` errors. Since we do not know the root cause it would be helpful to try to get as muc... — committed to Luap99/libpod by Luap99 2 years ago
readConmonPipeData: try to improve error Issue #10927 reports `container create failed (no logs from conmon): EOF` errors. Since we do not know the root cause it would be helpful to try to get as muc... — committed to gcalin/podman by Luap99 2 years ago
readConmonPipeData: try to improve error Issue #10927 reports `container create failed (no logs from conmon): EOF` errors. Since we do not know the root cause it would be helpful to try to get as muc... — committed to gcalin/podman by Luap99 2 years ago
readConmonPipeData: try to improve error Issue #10927 reports `container create failed (no logs from conmon): EOF` errors. Since we do not know the root cause it would be helpful to try to get as muc... — committed to mheon/libpod by Luap99 2 years ago
readConmonPipeData: try to improve error Issue #10927 reports `container create failed (no logs from conmon): EOF` errors. Since we do not know the root cause it would be helpful to try to get as muc... — committed to mheon/libpod by Luap99 2 years ago
readConmonPipeData: try to improve error Issue #10927 reports `container create failed (no logs from conmon): EOF` errors. Since we do not know the root cause it would be helpful to try to get as muc... — committed to gbraad-redhat/podman by Luap99 2 years ago
e2e: remove "-it" from podman run & exec ...at least as many as possible. "run/exec -it" make no sense in a CI environment; I believe the vast majority of these are the result of fingers typing on au... — committed to edsantiago/libpod by edsantiago a year ago
e2e: remove "-it" from podman run & exec ...at least as many as possible. "run/exec -it" make no sense in a CI environment; I believe the vast majority of these are the result of fingers typing on au... — committed to edsantiago/libpod by edsantiago a year ago
e2e: remove "-it" from podman run & exec ...at least as many as possible. "run/exec -it" make no sense in a CI environment; I believe the vast majority of these are the result of fingers typing on au... — committed to edsantiago/libpod by edsantiago a year ago
e2e: remove "-it" from podman run & exec ...at least as many as possible. "run/exec -it" make no sense in a CI environment; I believe the vast majority of these are the result of fingers typing on au... — committed to edsantiago/libpod by edsantiago a year ago
e2e: remove "-it" from podman run & exec ...at least as many as possible. "run/exec -it" make no sense in a CI environment; I believe the vast majority of these are the result of fingers typing on au... — committed to edsantiago/libpod by edsantiago a year ago
e2e: remove "-it" from podman run & exec ...at least as many as possible. "run/exec -it" make no sense in a CI environment; I believe the vast majority of these are the result of fingers typing on au... — committed to edsantiago/libpod by edsantiago a year ago
e2e: remove "-it" from podman run & exec ...at least as many as possible. "run/exec -it" make no sense in a CI environment; I believe the vast majority of these are the result of fingers typing on au... — committed to edsantiago/libpod by edsantiago a year ago
e2e: remove "-it" from podman run & exec ...at least as many as possible. "run/exec -it" make no sense in a CI environment; I believe the vast majority of these are the result of fingers typing on au... — committed to edsantiago/libpod by edsantiago a year ago
e2e: remove "-it" from podman run & exec ...at least as many as possible. "run/exec -it" make no sense in a CI environment; I believe the vast majority of these are the result of fingers typing on au... — committed to edsantiago/libpod by edsantiago a year ago
e2e: remove "-it" from podman run & exec ...at least as many as possible. "run/exec -it" make no sense in a CI environment; I believe the vast majority of these are the result of fingers typing on au... — committed to edsantiago/libpod by edsantiago a year ago
e2e: remove "-it" from podman run & exec ...at least as many as possible. "run/exec -it" make no sense in a CI environment; I believe the vast majority of these are the result of fingers typing on au... — committed to edsantiago/libpod by edsantiago a year ago
e2e: remove "-it" from podman run & exec ...at least as many as possible. "run/exec -it" make no sense in a CI environment; I believe the vast majority of these are the result of fingers typing on au... — committed to edsantiago/libpod by edsantiago a year ago

Most upvoted comments

@mgoltzsche thanks for the followup. It looks like your situation is a hard failure; the bug reported here is a flake, i.e., it fails unpredictably on a system that otherwise works fine. Hope you’re able to get a working crun.

edsantiago on Jun 23, 2022

Still active. int remote ubuntu-2110 root on April 12. Here’s the newly-improved logging, hope it helps:

         # podman-remote [options] exec -it test cat /etc/resolv.conf
         Error: container create failed (no logs from conmon): conmon bytes "": readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...
         time="2022-04-12T07:40:52Z" level=error msg="error attaching to container 4e927437ce760730eb3f42a5ae787ce6395f1bd2fe91c7f60cd1efe885f2a050 exec session 7d0bfd1f752051b6bfd9ca9e250976bf9518aec9167d829c87bfbf8b4ee944bb: container create failed (no logs from conmon): conmon bytes \"\": readObjectStart: expect { or n, but found \x00, error found in #0 byte of ...||..., bigger context ...||..."
         output: Error: container create failed (no logs from conmon): conmon bytes "": readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...

edsantiago on Apr 18, 2022