cannot open /run/user/1000/crun/.../exec.fifo: No such file or directory

[devurandom]

Describe the bug

Sometimes Podman Compose will be unable to start a pod / Compose environment, mentioning "cannot open /run/user/1000/crun/.../exec.fifo: No such file or directory" and "unable to start container ...: /usr/bin/crun start ... failed: exit status 1" as the error.

I split this out from #921, because in that report I encounter two different error messages -- either one or the other.

To Reproduce

Steps to reproduce the behavior: See #921 (comment).

Expected behavior

Pod starts.

Actual behavior

cannot open `/run/user/1000/crun/7eca407523df35a94fa118e422d514ac95b9796ee07cad2b6487e06931510b2e/exec.fifo`: No such file or directory
Error: unable to start container 7eca407523df35a94fa118e422d514ac95b9796ee07cad2b6487e06931510b2e: `/usr/bin/crun start 7eca407523df35a94fa118e422d514ac95b9796ee07cad2b6487e06931510b2e` failed: exit status 1

and then after a while (<60s ususally):

[REDACTED2]    | time="2024-11-08T15:44:42+01:00" level=warning msg="StopSignal SIGTERM failed to stop container [REDACTED3] in 10 seconds, resorting to SIGKILL"

and eventually:

WARNING:podman_compose:container did not shut down after 10 seconds, killing

Note that the "failed to stop container" message does not come right after the "unable to start container" message and not right before the "container did not shut down after 10 seconds" message. Significant (>10s) can pass between each message (while other containers still output their regular log messages).

Also note that the container mentioned in "unable to start container" and the container mentioned in "failed to stop container" are never the same and that the container mentioned as the source of the "failed to stop container" ("[REDACTED2]") is never the same container as the one mentioned in the message ("[REDACTED3]").

Output

❯ grep PRETTY /etc/os-release
PRETTY_NAME="Fedora Linux 41 (KDE Plasma)"

❯ podman-compose --version
podman-compose version 1.2.0
podman version 5.2.5

$ podman-compose up
Error: adding pod to state: name "[REDACTED]" is in use: pod already exists
Error: creating container storage: the container name "[REDACTED1]" is already in use by 7eca407523df35a94fa118e422d514ac95b9796ee07cad2b6487e06931510b2e. You have to remove that container to be able to reuse that name: that name is already in use, or use --replace to instruct Podman to do so.
Error: [... similar for other containers in the pod ...]
[REDACTED1]    | cannot open `/run/user/1000/crun/7eca407523df35a94fa118e422d514ac95b9796ee07cad2b6487e06931510b2e/exec.fifo`: No such file or directory
[REDACTED1]    | Error: unable to start container 7eca407523df35a94fa118e422d514ac95b9796ee07cad2b6487e06931510b2e: `/usr/bin/crun start 7eca407523df35a94fa118e422d514ac95b9796ee07cad2b6487e06931510b2e` failed: exit status 1
[... other containers starting ...]
[REDACTED2]    | time="2024-11-08T15:44:42+01:00" level=warning msg="StopSignal SIGTERM failed to stop container [REDACTED3] in 10 seconds, resorting to SIGKILL"
WARNING:podman_compose:container did not shut down after 10 seconds, killing
WARNING:podman_compose:container did not shut down after 10 seconds, killing

Environment:

• OS: Linux (see above)