-
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
Error: default OCI runtime "crun" not found: invalid argument (without sudo) #18483
Comments
Do you have a custom |
yes, I've got a custom
I also executed the
|
How did you login to your user? You should never use |
I'm logging with my user (dsalerno / My user has got sudo privilegies. Is there a way to clean up the environment? |
Did your uid change? Looks like the uid changed in the path that are stored in the libpod db. The only way to resolve this is to |
Ok, it worked, I probably restored a backup and the |
Issue Description
Executing
podman
with a command (i.e.version
,info
,run
,build
etc) without the sudo privileges, I'm receiving the following error:Error: default OCI runtime "crun" not found: invalid argument
I'm on Fedora 38 Intel based x86_64 bit system with podman and crun installed and I followed the rootless tutorial.
Steps to reproduce the issue
Steps to reproduce the issue
podman version
Error: default OCI runtime "crun" not found: invalid argument
sudo podman version
Describe the results you received
Describe the results you received
Describe the results you expected
I'm receiving an error like
crun
is not installed at all into the system, even if it is present and is working with sudo privilegespodman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
$ sudo podman version
$ sudo podman info
$ sudo rpm -q podman
podman-4.5.0-1.fc38.x86_64
Additional information
As you can see from the output of the
podman info
, SELinux is enabled.The text was updated successfully, but these errors were encountered: