This is a weird one. Only two occurrences (four, if you count retries within the same PR):
podman make sure once container is removed
/var/tmp/go/src/github.com/containers/podman/test/e2e/pod_initcontainers_test.go:101
[BeforeEach] Podman init containers
/var/tmp/go/src/github.com/containers/podman/test/e2e/pod_initcontainers_test.go:22
[It] podman make sure once container is removed
/var/tmp/go/src/github.com/containers/podman/test/e2e/pod_initcontainers_test.go:101
Running: podman [options] create --init-ctr once --pod new:foobar quay.io/libpod/alpine:latest bin/sh -c echo RvmaTMZpEbGBRJfg > /dev/shm/stbkBXTERreu
21d775a67a44bb9deee0d5895f7bcfaa8bfd553847d68f7c87895c9bea2861b6
Running: podman [options] create --pod foobar -t quay.io/libpod/alpine:latest top
c0b94e4017e4766be71b2f22ee9a11ab2d8e7a82503c6d8d4f43b39ce1430386
Running: podman [options] pod start foobar
1c69bbfba8a4ad47516cdad9162751c3f5b57672be2a835821c0a7892315ef97
Running: podman [options] container exists 21d775a67a44bb9deee0d5895f7bcfaa8bfd553847d68f7c87895c9bea2861b6
Running: podman [options] pod stop foobar
1c69bbfba8a4ad47516cdad9162751c3f5b57672be2a835821c0a7892315ef97
Running: podman [options] pod start foobar
1c69bbfba8a4ad47516cdad9162751c3f5b57672be2a835821c0a7892315ef97
Running: podman [options] exec -it c0b94e4017e4766be71b2f22ee9a11ab2d8e7a82503c6d8d4f43b39ce1430386 cat /dev/shm/stbkBXTERreu
RvmaTMZpEbGBRJfg <------- expected: ENOENT, also expected exit status 1 (actual is 0)
This init functionality is new to me, and I haven't poked deeply enough to grok the test, but from my limited understanding this failure mode just shouldn't be possible. Filing as a placeholder.
Podman init containers [It] podman make sure once container is removed
- fedora-33 : int podman fedora-33 root container
Only fedora 33, and only since September. But just in case it's related, Ubuntu also had a failure, albeit a different error message:
Running: podman [options] exec -it b474b315832e6bf6cfdd1d5110b710302ef380ac97035a0fa9ca3034f88ab110 cat /dev/shm/sKRCHOZzSNUg
Error: container create failed (no logs from conmon): EOF <--- yielding exit status 255, instead of the expected 1
- ubuntu-2104 : int podman ubuntu-2104 root host
This is a weird one. Only two occurrences (four, if you count retries within the same PR):
This init functionality is new to me, and I haven't poked deeply enough to grok the test, but from my limited understanding this failure mode just shouldn't be possible. Filing as a placeholder.
Podman init containers [It] podman make sure once container is removed
Only fedora 33, and only since September. But just in case it's related, Ubuntu also had a failure, albeit a different error message: