-
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
OCI Runtime Failed on upgrade #21024
Comments
Seems to be a conmon issue - I downgraded it ( |
Having the same issue here, the thing in the error message is garbled, and there are two new fifo file created named It's just another day running
|
Now the new upgrade of conmon to 1:2.1.9-2 solved these issue. Please |
For Ubuntu still waiting the build in https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/unstable/xUbuntu_22.04/amd64/ :/ For ubuntu 22.04, need to download and install wget https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_22.04/amd64/conmon_2.1.2~0_amd64.deb -O /tmp/conmon_2.1.2.deb
sudo apt install /tmp/conmon_2.1.2.deb |
THANK YOU! |
thank you |
@thanos1983 (sorry to mentioning you, I hope I don't mention wrong person), could someone at the cri-o end take the fix from conmon 2.1.9.-2 and trigger update/build on https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/unstable/xUbuntu_22.04/amd64/conmon_2:2.1.9-0ubuntu22.04+obs17.1_amd64.deb ? So the latest update for conmon 2.1.9-1 that's broken could be overrided when others update (I know it's a unstable branch, but seems for ubuntu user now almost everyone use podman 4.6.2 from opensuse build). like @8ar10der did on Arch Pkg (also some others on Fedora and RHEL/Clones seems already rebuilding). Thank you! EDIT: Fixed on 2.1.10 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/unstable/xUbuntu_22.04/amd64/conmon_2:2.1.10-0ubuntu22.04+obs18.2_amd64.deb thanks for @thanos1983 |
closing this is tracked by the conmon project |
Podman issue: containers/podman#21024 Conmon issue: containers/conmon#475 Signed-off-by: Sagi Shnaidman <sshnaidm@redhat.com>
Podman issue: containers/podman#21024 Conmon issue: containers/conmon#475 Signed-off-by: Sagi Shnaidman <sshnaidm@redhat.com>
Podman issue: containers/podman#21024 Conmon issue: containers/conmon#475 Signed-off-by: Sagi Shnaidman <sshnaidm@redhat.com>
Issue Description
EDIT: It seems to be an issue related to containers/conmon#475 as downgrading fixes it
I update my podman today to the latest version. When trying to run podman with any container, I get an error saying OCI runtime tried running a program that doesn't exist. I used WSL to fresh install as well to see if it was my system and was met with the same error. It was working great before the update, but stopped after updating, I believe I went from 4.7.2 to the latest, but I'm unsure.
Sometimes I also get the following error message when trying other containers.
DEBU[0004] ExitCode msg: "container create failed (no logs from conmon): conmon bytes \"\": readobjectstart: expect { or n, but found \x00, error found in #0 byte of ...||..., bigger context ...||..."
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
An error and no container starting up.
Describe the results you expected
The container to start
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Debug Log
The text was updated successfully, but these errors were encountered: