executable file `/catatonit` [et al] not found in $PATH: No such file or directory #17042

edsantiago · 2023-01-09T15:20:03Z

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
- PR Vendor in latest containers/common #17014
  - 01-06 15:32
fedora-37 : sys podman fedora-37 rootless host
- PR Add container error message to ContainerState #16806
  - 01-03 17:17

The text was updated successfully, but these errors were encountered:

edsantiago · 2023-01-24T14:56:00Z

New symptom, but I think it's likely to be the same root cause:

not ok 510 podman kube play read-only
...
# podman-remote --url unix:/tmp/podman_tmp_ytPc kube play --replace /tmp/podman_bats.aJCFSg/test.yml
Pods stopped:
7e51a461b3a474bd8acbec733d0459345e49789c441343a31f26546ebc2513e1
Pods removed:
Pods removed:
7e51a461b3a474bd8acbec733d0459345e49789c441343a31f26546ebc2513e1
Volumes removed:
Pod:
85546bc1df8e723b92108d6fc2ece0a81e04cd4df5b22353349f9045a6e2aaa2
Containers:
e9e0e350b1c41527bca2c69c5b7e7732dc4366f51a9e8bba0f84a26652839933
4ffd5b7234aa686162bcb82f9d1f033becd430fd34b565bd84ea3501f9b02d5f
69342bbfc7f1f6cda933ec17586078359fc3060caafd9f9de7490c5662739e91

starting container e9e0e350b1c41527bca2c69c5b7e7732dc4366f51a9e8bba0f84a26652839933: crun: executable file `touch` not found in $PATH: No such file or directory: OCI runtime attempted to invoke a command that was not found

Error: error tearing down workloads "json: cannot unmarshal string into Go struct field PodRmReport.RmReport.Err of type error" after kube play error "failed to start 1 containers"

Worse, though, this is one of those "leave-everything-hosed" issues. Subsequent pod rm fails:

# podman-remote --url unix:/tmp/podman_tmp_ytPc pod rm -t 0 -f -a
Error: 1 error occurred:
	* removing container 28abdcb12349964aa232cd84f5a0e8f72ff0b393636860b53e848d50e3c6f978 from pod 85546bc1df8e723b92108d6fc2ece0a81e04cd4df5b22353349f9045a6e2aaa2: removing container 28abdcb12349964aa232cd84f5a0e8f72ff0b393636860b53e848d50e3c6f978 root filesystem: 2 errors occurred:
	* deleting layer "0ca1bc5840cef6ce57fb0a660343b09a3868aaad4373e5ff7d733e5e21b6bc5f": unlinkat /var/lib/containers/storage/overlay/0ca1bc5840cef6ce57fb0a660343b09a3868aaad4373e5ff7d733e5e21b6bc5f/merged: device or resource busy
	* deleting layer "8d0f0581195fce5cde3bf490a3bded794b036f5a31d66a079386534301dfbb27": unlinkat /var/lib/containers/storage/overlay/8d0f0581195fce5cde3bf490a3bded794b036f5a31d66a079386534301dfbb27/merged: device or resource busy

...then more:

# podman-remote --url unix:/tmp/podman_tmp_ytPc image list --format {{.ID}} {{.Repository}}
timeout: sending signal TERM to command ‘/var/tmp/go/src/github.com/containers/podman/bin/podman-remote’

...and then (almost) all subsequent tests fail.

f37 remote root

dzintars · 2023-01-24T15:49:41Z

I got into this while trying to fix slow ZFS performace. I just installed fresh Fedora root on ZFS and got slow MySQL, podman build (COPY) and this one issue now. Still have no idea where it comes from, but i will leave this trail there while i'm there. First time i run Play, it went OK. Now it fails.

edsantiago · 2023-01-25T15:58:59Z

Someone please pay attention here. See also #17216.

fedora-36 : sys remote fedora-36 root host [remote]
- PR build(deps): bump github.com/onsi/gomega from 1.25.0 to 1.26.0 #17195
  - 01-24 08:48
fedora-37 : sys remote fedora-37 root host [remote]
- PR vendor in latests containers/(storage, common, build, image) #17155
  - 01-19 12:18

edsantiago · 2023-01-31T17:23:19Z

Another one, f37 remote rootless:

not ok 511 podman kube play read-only
$ podman-remote --url unix:/tmp/podman_tmp_KN8w kube play --replace /tmp/podman_bats.cs7isZ/test.yml
Pods stopped:
942cfb497e3a3263e13489ad7d1fc34b29ac696c25c2af184ffd07d7d6319643
Pods removed:
942cfb497e3a3263e13489ad7d1fc34b29ac696c25c2af184ffd07d7d6319643
Volumes removed:
Pod:
118559121f4ff7f5f8abcfea3619dcbc74a28f91735518dca6d52f8d3e5affff
Containers:
2e1cc5a0f26563b17becb1d22ed68b1ea5eea35c3e67a4f732f98b594e92fb5d
3bfb0392a9fcb094c7f81b4fa482c3393aa0253f738ffa6471cca1c0ecdd85f8
4a94393f3bd916e6c696759c61534f48aad43cc007cdca7e46ca970d6f6a917e

starting container 4a94393f3bd916e6c696759c61534f48aad43cc007cdca7e46ca970d6f6a917e: crun: executable file `touch` not found in $PATH: No such file or directory: OCI runtime attempted to invoke a command that was not found

Error: error tearing down workloads "json: cannot unmarshal string into Go struct field PodRmReport.RmReport.Err of type error" after kube play error "failed to start 1 containers"

All subsequent tests fail.

@containers/podman-maintainers pretty please TAL

edsantiago · 2023-02-06T13:37:42Z

Another one:

fedora-36 : sys remote fedora-36 root host [remote]
- PR [v4.4] make hack/markdown-preprocess parallel-safe #17360
  - 02-03 19:37 in [sys] podman kube play read-only

I just created a Jira issue for it, in hopes that it will get some attention. Unfortunately Jira disappears issues as soon as they're created, so I have no way of actually linking to it, sorry.

vrothberg · 2023-02-06T13:38:49Z

@edsantiago you can add the created issue to the current sprint. Then it'll pop up on the board.

edsantiago · 2023-02-06T13:39:40Z

@vrothberg what happened is, I created a Jira issue, there was a brief popup saying "Successfully created issue", and it disappeared, and now I don't know how to find it.

vrothberg · 2023-02-06T13:42:17Z

@edsantiago click on "Issues" in the top bar. Then select "Reported by me". The issue you've created should show up there.

edsantiago · 2023-02-06T13:50:39Z

Thank you! Issue is: https://issues.redhat.com/browse/RUN-1773 (Sorry, I can find no way to add it to a sprint.)

vrothberg · 2023-02-06T13:54:44Z

I moved it. Click on "Edit" then select the "Prioritization" field. Not intuitive but at some point I could recall.

github-actions · 2023-03-14T00:07:37Z

A friendly reminder that this issue had no activity for 30 days.

rhatdan · 2023-03-15T15:43:22Z

@edsantiago still an issue?

edsantiago · 2023-03-16T17:39:12Z

Yes, just today, f37 remote rootless, in a kube test:

[+1295s] not ok 526 podman kube play read-only
...
starting container f907f2aef743f7beb8fd611a95b0ae980ea8d663fa336fff70f40d544c933827: 
      crun: executable file `touch` not found in $PATH:
      No such file or directory:
      OCI runtime attempted to invoke a command that was not found

edsantiago · 2023-03-28T12:19:14Z

Two yesterday, in the same CI run:

fedora-37 : int podman fedora-37 rootless host boltdb
- PR Ed's pet PR with no flake retries #17831
  - 03-27 07:43 in Podman run networking [It] Aardvark Test 2: Two containers, same subnet
  - 03-27 07:43 in Podman run networking [It] Aardvark Test 3: Two containers, same subnet w/aliases

vrothberg · 2023-03-28T12:26:56Z

OK, this is not only /catatonit but many other commands and tests that fail as well.

@giuseppe could you take at a look at https://api.cirrus-ci.com/v1/artifact/task/4732541031153664/html/int-podman-fedora-37-rootless-host-boltdb.log.html#t--Aardvark-Test-2--Two-containers--same-subnet--1?

edsantiago · 2023-03-28T12:37:20Z

Plot twist: it just happened in debian with runc:

# podman-remote kube play --replace /tmp/podman_bats.MU5ITd/test.yml
starting container <sha>: runc: runc create failed: unable to start container process: exec: "touch":
      executable file not found in $PATH: OCI runtime attempted to invoke a command that was not found

Not only that, but we go into everything-hosed territory (#17216) after that failure.

vrothberg · 2023-03-28T12:47:52Z

Maybe it's just another symptom of the "everything's hosed" issue?

vrothberg · 2023-03-28T12:48:09Z

It seems to relate to exec in a way

giuseppe · 2023-03-29T07:33:14Z

this error usually happens when there is no storage mounted at that path and the rootfs directory is empty.

edsantiago · 2023-04-20T00:43:28Z

Another one today, f37 rootless.

So far we have this happening on debian, f36, f37. Root and rootless. Podman and podman-remote. boltdb and sqlite. int and sys tests.

edsantiago · 2023-04-26T12:16:57Z

This continues to happen. Yesterday I saw an interesting variation in f37 remote aarch64 root:

not ok 537 podman kube play read-only
...
# podman-remote kube play --replace /tmp/podman_bats.7MRfgJ/test.yml
starting container <CID>: workdir "/home/podman" does not exist on container <CID>

From there, of course, it goes into the unlinkat/EBUSY/hosed pit of despair.

This is a different symptom -- the typical one is "executable not found" -- but this is too close to be coincidence. To me, it all points to a problem unpacking or mounting images. And this is starting to scare me because the behavior seems to manifest as "random files/directories missing from container", which in turn can lead to countless failure possibilities.

edsantiago · 2023-04-27T16:36:10Z

Updated title. Removed 'crun', because this happens with runc too. I'm pretty sure it has nothing to do with the runtime, or if it does, it's maybe a race between unpacking image and starting runtime.

edsantiago · 2023-05-01T17:57:13Z

I am treating this as a weird variation of this bug:

not ok 242 podman kill - test signal handling in containers
...
$ podman run -d quay.io/libpod/testimage:20221018 sh -c for i in 1 2 3 4 5 6 8 10 12 13 14 15 16 20 21 22 23 24 25 26 64; do trap "echo got: $i" $i; done;
        echo READY;
        while ! test -e /stop; do sleep 0.1; done;
        echo DONE
e6e85baacc7c04c9312b3650aeb82bb877e4f8e17a32f8d3511996137fef1772
time="2023-05-01T12:00:53-05:00" level=error msg="Failed to get journal entry: failed to read journal entry: error resolving symbol \"sd_journal_enumerate_data\": libsystemd-journal.so.0: cannot open shared object file: No such file or directory"

edsantiago · 2023-05-02T12:14:14Z

Here's another variation, f38 rootless, where a subsequent network rm gets the "FS magic" flake (#17903):

$ podman [options] exec aone dig +short atwo
Error: crun: executable file `dig` not found in $PATH: No such file or directory: OCI runtime attempted to invoke a command that was not found
[repeat five more times]

$ podman [options] network rm -f Testd8dc524952
time="2023-05-02T06:23:22-05:00" level=error msg="getting rootless network namespace: unknown FS magic on \"/run/user/3031/netns/rootless-netns-ea85f07403a18951a2fc\": 1021994"
time="2023-05-02T06:23:22-05:00" level=error msg="Unable to clean up network for container 7a0d923968fcdd14098c5f5eadcdc73f93f37e219efeae14622af0e77caf597e: \"unmounting network namespace for container 7a0d923968fcdd14098c5f5eadcdc73f93f37e219efeae14622af0e77caf597e: failed to unmount NS: at /run/user/3031/netns/netns-e52d9c8b-fee2-7d11-a237-1df80a9c2157: invalid argument\""
time="2023-05-02T06:23:22-05:00" level=error msg="getting rootless network namespace: unknown FS magic on \"/run/user/3031/netns/rootless-netns-ea85f07403a18951a2fc\": 1021994"
time="2023-05-02T06:23:22-05:00" level=error msg="Unable to clean up network for container e63334413cd64415273903ca641139ca450ad9af59589ea9c0f284d4a2e432e6: \"unmounting network namespace for container e63334413cd64415273903ca641139ca450ad9af59589ea9c0f284d4a2e432e6: failed to unmount NS: at /run/user/3031/netns/netns-30567630-8c68-c167-e0f4-a8c650707a87: invalid argument\""

Luap99 · 2023-05-02T12:30:24Z

If these are only rootless then it could be the same problem (killed pause process). Basically the exec ends up in a different mountns so it cannot see the overlay container mount thus the mountpoint is empty and the exec fails.

But I don't really see the connection the the other errors in the system test as these things shouldn't happen there.

edsantiago · 2023-05-02T12:41:41Z

The overall issue is not rootless; here's the list of incidents as of right now. Please, huge grain of salt, because some of the logs below are different manifestations that I believe are the same issue, but I can easily be wrong.

debian-12 : sys remote debian-12 root host boltdb [remote]
- PR Add sha256: to images history id for docker compatibility #18327
  - 04-26 15:52 in [sys] podman kube play read-only
- PR CI: enable sqlite system tests #17954
  - 03-28-2023 08:31 in [sys] podman kube play read-only
- PR build(deps): bump google.golang.org/protobuf from 1.29.0 to 1.30.0 #17814
  - 03-16-2023 10:19 in [sys] podman kube play read-only
fedora-36 : sys podman fedora-36 rootless host
- PR Vendor in latest containers/common #17014
  - 01-06-2023 15:32 in [sys] 500 podman play --service-container
fedora-36 : sys remote fedora-36 root host [remote]
- PR [v4.4] make hack/markdown-preprocess parallel-safe #17360
  - 02-03-2023 19:37 in [sys] podman kube play read-only
- PR build(deps): bump github.com/onsi/gomega from 1.25.0 to 1.26.0 #17195
  - 01-24-2023 08:48 in [sys] podman kube play read-only
fedora-37 : int podman fedora-37 rootless host boltdb
- PR Ed's pet PR with no flake retries #17831
  - 04-19 17:31 in Podman run networking [It] podman verify network scoped DNS server and also verify updating network dns server
  - 03-27-2023 07:43 in Podman run networking [It] Aardvark Test 2: Two containers, same subnet
  - 03-27-2023 07:43 in Podman run networking [It] Aardvark Test 3: Two containers, same subnet w/aliases
fedora-37 : int podman fedora-37 rootless host sqlite
- PR Ed's pet PR with no flake retries #17831
  - 03-28-2023 17:00 in Podman run networking [It] podman verify network scoped DNS server and also verify updating network dns server
  - 03-28-2023 11:40 in Podman run networking [It] podman verify network scoped DNS server and also verify updating network dns server
fedora-37 : sys podman fedora-37 rootless host
- PR Add container error message to ContainerState #16806
  - 01-03-2023 17:17 in [sys] 491 podman play --service-container
fedora-37 : sys podman fedora-37 rootless host sqlite
- PR Ed's pet PR with no flake retries #17831
  - 05-01 13:17 in [sys] podman kill - test signal handling in containers
fedora-37 : sys remote fedora-37 root host [remote]
- PR vendor in latests containers/(storage, common, build, image) #17155
  - 01-19-2023 12:18 in [sys] podman kube play read-only
fedora-37 : sys remote fedora-37 rootless host [remote]
- PR [NO NEW TESTS NEEDED] Fixes port collision issue on use of --publish-all #17291
  - 01-31-2023 07:51 in [sys] podman kube play read-only
fedora-37 : sys remote fedora-37 rootless host boltdb [remote]
- PR Vendor in latest containers/(storage, common, image) #17815
  - 03-16-2023 10:49 in [sys] podman kube play read-only
fedora-37-aarch64 : sys remote fedora-37-aarch64 root host sqlite [remote]
- PR Ed's pet PR with no flake retries #17831
  - 04-25 21:04 in [sys] podman kube play read-only
fedora-38 : int podman fedora-38 rootless host boltdb
- PR Ed's pet PR with no flake retries #17831
  - 05-02 07:30 in Podman run networking [It] Aardvark Test 1: One container
  - 05-02 07:30 in Podman run networking [It] Aardvark Test 2: Two containers, same subnet

edsantiago · 2023-05-25T12:05:54Z

I'm seeing a strong correlation between this bug and the unlinkat-ebusy one (#17216).

edsantiago · 2023-06-14T23:47:12Z

Another one, debian root remote, and now this one is followed by unmounting/EINVAL (#18831) instead of unlinkat/EBUSY.

edsantiago · 2023-07-13T11:45:39Z

Here's a completely baffling one:

[+0323s] not ok 123 podman logs - --until --follow k8s-file
...
<+039ms> # # podman run --log-driver=k8s-file --name iW0TN8JkHe -d quay.io/libpod/testimage:20221018 sh -c n=1;while :; do echo Z9FGyLq2HO--$n; n=$((n+1));sleep 0.1; done
<+270ms> # 4616840454fd99ee2f98a8ad0038a81a778c30e23982dc3e743766b20a5e4ce6
<+009ms> # # podman logs --until 3s -f iW0TN8JkHe
<+3.05s> # Z9FGyLq2HO--1
         # time="2023-07-12T14:22:51-05:00" level=warning msg="cannot set data threshold: error resolving symbol \"sd_journal_set_data_threshold\": libsystemd-journal.so.0: cannot open shared object file: No such file or directory"
         # Z9FGyLq2HO--2
         # Z9FGyLq2HO--3
         # Z9FGyLq2HO--4

I can't tell if the spurious message is coming from podman logs or from podman run. I also can't tell if this is related to the missing-logs flake, #18501, which I've spent most of this bug week unsuccessfully trying to reproduce.

odockal · 2023-08-16T16:15:19Z

I have encounter something similar when trying a docker-compose with a podman 4.6.1 installed via podman desktop. Check out this issue-3560 in podman desktop repo pls.

edsantiago · 2023-10-03T19:27:06Z

Another one (remote f39beta root) where "crun can't find touch", then everything gets hosed:

[+1232s] not ok 591 podman kube play read-only
...
<+068ms> # # podman-remote --url unix:///tmp/podman_tmp_dVRg kube play --replace /tmp/podman_bats.60PZ2z/test.yml
<+1.23s> # Pods stopped:
         # 20132e558e28f8aed193c9faf8ba5aa58e2fb799556b784c4f85b31790cd4442
         # Pods removed:
         # 20132e558e28f8aed193c9faf8ba5aa58e2fb799556b784c4f85b31790cd4442
         # Secrets removed:
         # Volumes removed:
         # Pod:
         # fd3dfd6dd9b85b0ae9fce22cf368783f39155fcc275d100971a0068fe1625f23
         # Containers:
         # 64710c679e18906ed3a4f79a4d14558ebff4d1355020af76d563f8a6f8df970f
         # 53ef8353cb11071772dcff166d98f6c65b1db801bce252175ddddc53fa4e6394
         # 03c6affb6ff54077ffe1c10fe09586c70e87c87a90ca34260c602451cf509ca9
         #
         # starting container 64710c679e18906ed3a4f79a4d14558ebff4d1355020af76d563f8a6f8df970f: crun: executable file `touch` not found in $PATH: No such file or directory: OCI runtime attempted to invoke a command that was not found
         #
         # Error: failed to start 1 containers
<+009ms> # [ rc=125 (** EXPECTED 0 **) ]

Then, after that, all tests fail with:

<+014ms> # # podman-remote --url unix:///tmp/podman_tmp_dVRg rm -f 64710c679e18
<+045ms> # Error: removing storage for container "64710c679e18": removing mount point "/var/lib/containers/storage/overlay/7023308de3a259c3392a50eccd9b855ae7d6a9a7a4d8590f6da1975e79b7805c/merged": device or resource busy

This looks a LOT like #18831 and all of its everything-is-hosed variations, but here the strings "umount" or "unmount" do not appear in the error logs, so, keeping separate. Anyhow, @giuseppe, maybe there's a connection? Here are the recent ones:

fedora-37 : sys podman fedora-37 rootless host boltdb
- PR e2e: more ExitCleanly() on more test files #19959
  - 09-13 10:39 in [sys] [email protected] template
fedora-39? : sys remote fedora-39? root host sqlite [remote]
- PR windows: Use prebuilt gvproxy/win-sshproxy binaries #20202
  - 10-02 09:15 in [sys] podman kube play read-only from containers.conf

Seen in: sys podman/remote fedora-37/fedora-39? root/rootless host boltdb/sqlite

Move the execution of RecordWrite() before the graphDriver Cleanup(). This addresses a longstanding issue that occurs when the Podman cleanup process is forcely terminated and on some occasions the termination happens after the Cleanup() but before the change is recorded. This causes that the next user is not notified about the change and will mount the container without the home directory below (the infamous /var/lib/containers/storage/overlay mount). Then when the next time the graphDriver is initialized, the home directory is mounted on top of the existing mounts causing some containers to fail with ENOENT since all files are hidden and some others cannot be cleaned up since their mount directory is covered by the home directory mount. Closes: containers/podman#18831 Closes: containers/podman#17216 Closes: containers/podman#17042 Signed-off-by: Giuseppe Scrivano <[email protected]>

edsantiago · 2023-10-06T01:04:25Z

Not fixed. Flaked in my PR with c/storage vendored in. remote f39 root:

[It] podman ensure always init containers always run
...
# podman-remote [options] create --pod foobar -t quay.io/libpod/alpine:latest top
18b89aa07de8ead06331d7a38806eca61b6661ee9783b6d4d998a7218251fa37
# podman-remote [options] pod start foobar
d8d27e61637fd7db3f79af43dac1b881c3e19ff02be584ca484d534f98150bed
# podman-remote [options] exec 18b89aa07de8ead06331d7a38806eca61b6661ee9783b6d4d998a7218251fa37 cat /dev/shm/TXLQjCRunbCg
22:25:16.540067400
# podman-remote [options] pod stop foobar
d8d27e61637fd7db3f79af43dac1b881c3e19ff02be584ca484d534f98150bed
# podman-remote [options] pod start foobar
time="2023-10-05T17:25:18-05:00" level=error msg="Storage for container 18b89aa07de8ead06331d7a38806eca61b6661ee9783b6d4d998a7218251fa37 has been removed"
Error: starting container 18b89aa07de8ead06331d7a38806eca61b6661ee9783b6d4d998a7218251fa37: crun: executable file `top` not found in $PATH: No such file or directory: OCI runtime attempted to invoke a command that was not found

giuseppe · 2023-10-07T21:47:45Z

Not fixed. Flaked in my PR with c/storage vendored in. remote f39 root:

yeah, this is a different flake.

I think it is fixed with #20299

Without the PR, I could reproduce the flake with the following script (it would reproduce in around 5 minutes on a CI machine):

#!/bin/sh

set -xeuo pipefail

PODMAN=bin/podman-remote

filename="/dev/shm/foo123"
$PODMAN create --init-ctr always --net host --pod new:foobar fedora /bin/sh -c "date +%T.%N >  $filename"
$PODMAN create --name verify  --net host --pod foobar -t alpine top
$PODMAN pod start foobar
$PODMAN pod stop foobar
$PODMAN pod start foobar
$PODMAN rm -fa
$PODMAN pod rm -fa

and run it in a loop.

It is already running for longer than an hour with the patch

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, always check if the mountpoint is really present before skipping the mount. [NO NEW TESTS NEEDED] Closes: containers#17042 Signed-off-by: Giuseppe Scrivano <[email protected]>

edsantiago added flakes Flakes from Continuous Integration rootless kind/bug Categorizes issue or PR as related to a bug. labels Jan 9, 2023

edsantiago mentioned this issue Jan 25, 2023

unlinkat/EBUSY/hosed is back (Jan 2023) #17216

Closed

github-actions bot added the stale-issue label Mar 14, 2023

github-actions bot removed the stale-issue label Mar 16, 2023

edsantiago changed the title ~~Error: crun: executable file /catatonit not found in $PATH: No such file or directory~~ executable file /catatonit [et al] not found in $PATH: No such file or directory Apr 27, 2023

edsantiago mentioned this issue Jun 21, 2023

podman logs: missing output #18501

Closed

cdrage mentioned this issue Aug 21, 2023

Compose does not work with a rootless podman machine on windows podman-desktop/podman-desktop#3560

Closed

edsantiago mentioned this issue Sep 26, 2023

unmounting/EINVAL flake #18831

Closed

giuseppe mentioned this issue Oct 4, 2023

store: call RecordWrite() before graphDriver Cleanup() containers/storage#1724

Merged

flouthoc closed this as completed in containers/storage#1724 Oct 5, 2023

edsantiago reopened this Oct 6, 2023

giuseppe mentioned this issue Oct 7, 2023

container: always check if mountpoint is mounted #20299

Merged

openshift-ci bot closed this as completed in #20299 Oct 9, 2023

edsantiago mentioned this issue Nov 2, 2023

podman logs: error resolving symbol "sd_journal_xxx": libsystemd-journal.so.0: cannot open shared object file: ENOENT #20569

Closed

github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Jan 8, 2024

github-actions bot locked as resolved and limited conversation to collaborators Jan 8, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

executable file `/catatonit` [et al] not found in $PATH: No such file or directory #17042

executable file `/catatonit` [et al] not found in $PATH: No such file or directory #17042

edsantiago commented Jan 9, 2023 •

edited

Loading

edsantiago commented Jan 24, 2023

dzintars commented Jan 24, 2023

edsantiago commented Jan 25, 2023

edsantiago commented Jan 31, 2023

edsantiago commented Feb 6, 2023

vrothberg commented Feb 6, 2023

edsantiago commented Feb 6, 2023

vrothberg commented Feb 6, 2023

edsantiago commented Feb 6, 2023 •

edited

Loading

vrothberg commented Feb 6, 2023

github-actions bot commented Mar 14, 2023

rhatdan commented Mar 15, 2023

edsantiago commented Mar 16, 2023

edsantiago commented Mar 28, 2023

vrothberg commented Mar 28, 2023

edsantiago commented Mar 28, 2023

vrothberg commented Mar 28, 2023

vrothberg commented Mar 28, 2023

giuseppe commented Mar 29, 2023

edsantiago commented Apr 20, 2023

edsantiago commented Apr 26, 2023

edsantiago commented Apr 27, 2023

edsantiago commented May 1, 2023

edsantiago commented May 2, 2023

Luap99 commented May 2, 2023

edsantiago commented May 2, 2023

edsantiago commented May 25, 2023

edsantiago commented Jun 14, 2023

edsantiago commented Jul 13, 2023

odockal commented Aug 16, 2023

edsantiago commented Oct 3, 2023

edsantiago commented Oct 6, 2023

giuseppe commented Oct 7, 2023

executable file /catatonit [et al] not found in $PATH: No such file or directory #17042

executable file /catatonit [et al] not found in $PATH: No such file or directory #17042

Comments

edsantiago commented Jan 9, 2023 • edited Loading

Issue Description

edsantiago commented Jan 24, 2023

dzintars commented Jan 24, 2023

edsantiago commented Jan 25, 2023

edsantiago commented Jan 31, 2023

edsantiago commented Feb 6, 2023

vrothberg commented Feb 6, 2023

edsantiago commented Feb 6, 2023

vrothberg commented Feb 6, 2023

edsantiago commented Feb 6, 2023 • edited Loading

vrothberg commented Feb 6, 2023

github-actions bot commented Mar 14, 2023

rhatdan commented Mar 15, 2023

edsantiago commented Mar 16, 2023

edsantiago commented Mar 28, 2023

vrothberg commented Mar 28, 2023

edsantiago commented Mar 28, 2023

vrothberg commented Mar 28, 2023

vrothberg commented Mar 28, 2023

giuseppe commented Mar 29, 2023

edsantiago commented Apr 20, 2023

edsantiago commented Apr 26, 2023

edsantiago commented Apr 27, 2023

edsantiago commented May 1, 2023

edsantiago commented May 2, 2023

Luap99 commented May 2, 2023

edsantiago commented May 2, 2023

edsantiago commented May 25, 2023

edsantiago commented Jun 14, 2023

edsantiago commented Jul 13, 2023

odockal commented Aug 16, 2023

edsantiago commented Oct 3, 2023

edsantiago commented Oct 6, 2023

giuseppe commented Oct 7, 2023

executable file `/catatonit` [et al] not found in $PATH: No such file or directory #17042

executable file `/catatonit` [et al] not found in $PATH: No such file or directory #17042

edsantiago commented Jan 9, 2023 •

edited

Loading

edsantiago commented Feb 6, 2023 •

edited

Loading