Closed averyfreeman closed 3 years ago
@averyfreeman do you see this when you upgrade to 2.1.1 as well?
@averyfreeman do you see this when you upgrade to 2.1.1 as well?
I haven't tried it yet. I will do some tests locally on an essentially identical setup and let you know what I find out. Thanks :)
A friendly reminder that this issue had no activity for 30 days.
I figure this worked, so closing, reopen if I am mistaken.
BUG REPORT or FEATURE REQUEST?
/kind bug
Description
Steps to reproduce:
Upgrade podman amd64 from 2.0.5\~2 to 2.0.6\~2 via apt/dpkg
Reboot machine (not sure if relevant, but was step I took)
run pod
$ podman pod start <podname>
Received result:
error starting container /proc/16142/ns/pid OCI runtime command not found
Expected result:
podman starting pod
Other info:
I'm submitting this bug report just so you're aware of the issue I had, even though I managed to fix it (somewhat clunkily).
The pod start error happened consistently (there were no alternative outcomes). Always looking for same pid.
Was attempting to start pod as user (not root).
I'm using overlayfs and crun:
I tried deleting
/run/user/$UID/libpod/pause.pid
, same outcomeI ended up deleting
~/.local/share/containers/storage/
and~/.config/containers/storage/
with simplerm -rf
, and re-importing my pod tar.Output of
podman version
: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?
Yes, both
Additional environment details (AWS, VirtualBox, physical, etc.): hyper-expert VPS (appears to be KVM 440FX VM w/ virtio net + disk):
lshw output: