-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to add pause process to systemd sandbox cgroup #12065
Comments
Interestingly, this doesn't always happen. I just tried it again and did not receive this error message. But the next two times I ran it, I did get the error. |
I still get the error after
|
OK so far it looks like I do not get this error if I do |
Why does |
check that the pause pid exists before trying to move it to a separate scope. Closes: containers#12065 Signed-off-by: Giuseppe Scrivano <[email protected]>
commit 6b3b0a1 introduced a check for the PID file before attempting to move the PID to a new scope. This is still vulnerable to TOCTOU race condition though, since the PID file or the PID can be removed/killed after the check was successful but before it was used. Closes: containers#12065 [NO NEW TESTS NEEDED] it fixes a CI flake Signed-off-by: Giuseppe Scrivano <[email protected]>
check that the pause pid exists before trying to move it to a separate scope. Closes: containers#12065 Signed-off-by: Giuseppe Scrivano <[email protected]>
commit 6b3b0a1 introduced a check for the PID file before attempting to move the PID to a new scope. This is still vulnerable to TOCTOU race condition though, since the PID file or the PID can be removed/killed after the check was successful but before it was used. Closes: containers#12065 [NO NEW TESTS NEEDED] it fixes a CI flake Signed-off-by: Giuseppe Scrivano <[email protected]>
Reopening due to failure in bodhi gating tests (rootless):
Packages:
|
Closing again. I think this is another one of those "fixed a long long time ago" bugs that hasn't actually propagated into whatever is being built in f36. |
...and reopening again. This has just triggered in PR #11795 (the monster f35 Cirrus one), in f35 rootless:
(the PR is rebased on main @ f031bd2, which includes the purported fix (#12126) |
Oh, I guessed it was b/c of the 0.1.7 update PR. I rebased, let's see if it happens again. |
...and again. At this point it is no longer a flake, it is a showstopper. |
@giuseppe PTAL ASAP. |
@edsantiago opened a PR: #12323 |
we try hard to re-use the existing podman-pause.scope name when it already exists, causing any sort of race errors when the already existing scope is terminating. There is no such a requirement though, so just try with a random name. Closes: containers#12065 [NO NEW TESTS NEEDED] it fixes a race in the CI Signed-off-by: Giuseppe Scrivano <[email protected]>
[Backport of containers#12323 into v3.4, to fix gating-test flakes] we try hard to re-use the existing podman-pause.scope name when it already exists, causing any sort of race errors when the already existing scope is terminating. There is no such a requirement though, so just try with a random name. Closes: containers#12065 [NO NEW TESTS NEEDED] it fixes a race in the CI Signed-off-by: Giuseppe Scrivano <[email protected]>
we try hard to re-use the existing podman-pause.scope name when it already exists, causing any sort of race errors when the already existing scope is terminating. There is no such a requirement though, so just try with a random name. Closes: containers#12065 [NO NEW TESTS NEEDED] it fixes a race in the CI Signed-off-by: Giuseppe Scrivano <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue:
podman system reset
Describe the results you received:
[chris@fovo ~]$ podman --log-level debug system reset
INFO[0000] podman filtering at log level debug
DEBU[0000] Called reset.PersistentPreRunE(podman --log-level debug system reset)
DEBU[0000] Merged system config "/usr/share/containers/containers.conf"
DEBU[0000] Using conmon: "/usr/bin/conmon"
DEBU[0000] Initializing boltdb state at /home/chris/.local/share/containers/storage/libpod/bolt_state.db
DEBU[0000] Using graph driver btrfs
DEBU[0000] Using graph root /home/chris/.local/share/containers/storage
DEBU[0000] Using run root /run/user/1000/containers
DEBU[0000] Using static dir /home/chris/.local/share/containers/storage/libpod
DEBU[0000] Using tmp dir /run/user/1000/libpod/tmp
DEBU[0000] Using volume path /home/chris/.local/share/containers/storage/volumes
DEBU[0000] Set libpod namespace to ""
DEBU[0000] Not configuring container store
DEBU[0000] Initializing event backend journald
DEBU[0000] configured OCI runtime kata initialization failed: no valid executable found for OCI runtime kata: invalid argument
DEBU[0000] configured OCI runtime runsc initialization failed: no valid executable found for OCI runtime runsc: invalid argument
DEBU[0000] configured OCI runtime runc initialization failed: no valid executable found for OCI runtime runc: invalid argument
DEBU[0000] Using OCI runtime "/usr/bin/crun"
INFO[0000] Found CNI network podman (type=bridge) at /home/chris/.config/cni/net.d/87-podman.conflist
DEBU[0000] Default CNI network name podman is unchangeable
INFO[0000] podman filtering at log level debug
DEBU[0000] Called reset.PersistentPreRunE(podman --log-level debug system reset)
DEBU[0000] cached value indicated that overlay is supported
DEBU[0000] Merged system config "/usr/share/containers/containers.conf"
DEBU[0000] cached value indicated that overlay is supported
DEBU[0000] Using conmon: "/usr/bin/conmon"
DEBU[0000] Initializing boltdb state at /home/chris/.local/share/containers/storage/libpod/bolt_state.db
DEBU[0000] Using graph driver btrfs
DEBU[0000] Using graph root /home/chris/.local/share/containers/storage
DEBU[0000] Using run root /run/user/1000/containers
DEBU[0000] Using static dir /home/chris/.local/share/containers/storage/libpod
DEBU[0000] Using tmp dir /run/user/1000/libpod/tmp
DEBU[0000] Using volume path /home/chris/.local/share/containers/storage/volumes
DEBU[0000] cached value indicated that overlay is supported
DEBU[0000] Set libpod namespace to ""
DEBU[0000] [graphdriver] trying provided driver "btrfs"
DEBU[0000] Initializing event backend journald
DEBU[0000] configured OCI runtime runc initialization failed: no valid executable found for OCI runtime runc: invalid argument
DEBU[0000] configured OCI runtime kata initialization failed: no valid executable found for OCI runtime kata: invalid argument
DEBU[0000] configured OCI runtime runsc initialization failed: no valid executable found for OCI runtime runsc: invalid argument
DEBU[0000] Using OCI runtime "/usr/bin/crun"
INFO[0000] Found CNI network podman (type=bridge) at /home/chris/.config/cni/net.d/87-podman.conflist
DEBU[0000] Default CNI network name podman is unchangeable
DEBU[0000] Podman detected system restart - performing state refresh
INFO[0000] Setting parallel job count to 25
WARNING! This will remove:
- all containers
- all pods
- all images
- all build cache
Are you sure you want to continue? [y/N] y
DEBU[0001] cached value indicated that overlay is supported
DEBU[0001] Merged system config "/usr/share/containers/containers.conf"
DEBU[0001] cached value indicated that overlay is supported
DEBU[0001] Using conmon: "/usr/bin/conmon"
DEBU[0001] Initializing boltdb state at /home/chris/.local/share/containers/storage/libpod/bolt_state.db
DEBU[0001] Using graph driver btrfs
DEBU[0001] Using graph root /home/chris/.local/share/containers/storage
DEBU[0001] Using run root /run/user/1000/containers
DEBU[0001] Using static dir /home/chris/.local/share/containers/storage/libpod
DEBU[0001] Using tmp dir /run/user/1000/libpod/tmp
DEBU[0001] Using volume path /home/chris/.local/share/containers/storage/volumes
DEBU[0001] cached value indicated that overlay is supported
DEBU[0001] Set libpod namespace to ""
DEBU[0001] Initializing event backend journald
DEBU[0001] configured OCI runtime runc initialization failed: no valid executable found for OCI runtime runc: invalid argument
DEBU[0001] configured OCI runtime kata initialization failed: no valid executable found for OCI runtime kata: invalid argument
DEBU[0001] configured OCI runtime runsc initialization failed: no valid executable found for OCI runtime runsc: invalid argument
DEBU[0001] Using OCI runtime "/usr/bin/crun"
INFO[0001] Found CNI network podman (type=bridge) at /home/chris/.config/cni/net.d/87-podman.conflist
DEBU[0001] Default CNI network name podman is unchangeable
DEBU[0001] [graphdriver] trying provided driver "btrfs"
A storage.conf file exists at /home/chris/.config/containers/storage.conf
You should remove this file if you did not modified the configuration.
WARN[0001] Failed to add pause process to systemd sandbox cgroup:
[chris@fovo ~]$
Describe the results you expected:
Should reset without error.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
No
Additional environment details (AWS, VirtualBox, physical, etc.):
Fedora 35 Workstation, installed on a Lenovo Thinkpad
The text was updated successfully, but these errors were encountered: