Skip to content
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] Unable to start rootless container created by distrobox with podman and runc v1.2.0~rc1 #1359

Closed
fcrozat opened this issue Apr 30, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@fcrozat
Copy link

fcrozat commented Apr 30, 2024

This is a continuation of openSUSE Tumbleweed bug report: https://bugzilla.suse.com/show_bug.cgi?id=1222499

On openSUSE Tumbleweed with runc 1.2.0~rc1, distrobox created containers with podman/rootless won't start:
Error: unable to start container "988cc7b326ef04596a3d14ccc41bbdb43c74a6420b5e476b5da00b4e381f0d6f": runc: runc create failed: unable to start container process: error during container init: error mounting "/" to rootfs at "/run/host": mount dst=/run/host, dstFd=/proc/thread-self/fd/8, flags=0x5020: operation not permitted: OCI permission denied"

This works fine with older runc or with crun.

To reproduce:

DBX_CONTAINER_MANAGER="podman" distrobox create --image fedora:latest --name fedora -a "--runtime runc"

DBX_CONTAINER_MANAGER="podman" distrobox enter fedora

this will fail at "enter" command.

However:

distrobox rm -f fedora (to do the cleanup)

DBX_CONTAINER_MANAGER="podman" distrobox create --image fedora:latest --name fedora -a "--runtime crun"

DBX_CONTAINER_MANAGER="podman" distrobox enter fedora

will work nicely

@fcrozat fcrozat added the bug Something isn't working label Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant