podman: executable file `/catatonit` [et al] not found in $PATH: No such file or directory
Issue Description
Weird new flake, seen twice so far, both times in the same test:
not ok 491 podman play --service-container
...
$ podman pod restart test_pod
time="2023-01-03T16:16:36-06:00" level=error msg="Storage for container 36a44967cfc50aa8815018d902e09ab5a55fb0a8da70a9180a96c64bf6ed0685 has been removed"
Error: crun: executable file `/catatonit` not found in $PATH: No such file or directory: OCI runtime attempted to invoke a command that was not found
[ rc=125 (** EXPECTED 0 **) ]
- fedora-36 : sys podman fedora-36 rootless host
- fedora-37 : sys podman fedora-37 rootless host
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 33 (10 by maintainers)
Commits related to this issue
- store: call RecordWrite() before graphDriver Cleanup() Move the execution of RecordWrite() before the graphDriver Cleanup(). This addresses a longstanding issue that occurs when the Podman cleanup pr... — committed to giuseppe/storage by giuseppe 9 months ago
- container: always check if mountpoint is mounted when running as a service, the c.state.Mounted flag could get out of sync if the container is cleaned up through the cleanup process. To avoid this, ... — committed to giuseppe/libpod by giuseppe 9 months ago
- container: always check if mountpoint is mounted when running as a service, the c.state.Mounted flag could get out of sync if the container is cleaned up through the cleanup process. To avoid this, ... — committed to giuseppe/libpod by giuseppe 9 months ago
- container: always check if mountpoint is mounted when running as a service, the c.state.Mounted flag could get out of sync if the container is cleaned up through the cleanup process. To avoid this, ... — committed to giuseppe/libpod by giuseppe 9 months ago
- container: always check if mountpoint is mounted when running as a service, the c.state.Mounted flag could get out of sync if the container is cleaned up through the cleanup process. To avoid this, ... — committed to giuseppe/libpod by giuseppe 9 months ago
- container: always check if mountpoint is mounted when running as a service, the c.state.Mounted flag could get out of sync if the container is cleaned up through the cleanup process. To avoid this, ... — committed to giuseppe/libpod by giuseppe 9 months ago
- container: always check if mountpoint is mounted when running as a service, the c.state.Mounted flag could get out of sync if the container is cleaned up through the cleanup process. To avoid this, ... — committed to edsantiago/libpod by giuseppe 9 months ago
- container: always check if mountpoint is mounted when running as a service, the c.state.Mounted flag could get out of sync if the container is cleaned up through the cleanup process. To avoid this, ... — committed to edsantiago/libpod by giuseppe 9 months ago
I moved it. Click on “Edit” then select the “Prioritization” field. Not intuitive but at some point I could recall.