crun permission error starting distrobox container
I can create a distrobox container with
distrobox create -n arch -i archlinux:base-devel, but I can't start it: when I run distrobox enter arch, the following error is printed:
The permissions on that directory's parent are:
I get the same error using any other image, too (tested Fedora and Ubuntu).
However, if I make a container directly using Podman, it works fine, using either podman run --rm -it archlinux:base-devel, or podman create --name arch2 -i archlinux:base-devel then podman exec -it arch2 sh.
I've tried running podman system reset a couple times, as well as completely deleting the .local/share/containers directory (I didn't have any other containers prior to creating the distrobox), but this error still occurs with any new distrobox I create. How can I debug this issue? I've found a couple other posts on this Discord reporting similar errors, but there weren't clear resolutions for any of them.12 Replies
not sure i can even help since we cannot replicate the issue but do you dual boot windows and use the winbtrfs driver in windows?
i dual boot but i don't use winbtrfs, windows is on a separate ntfs partition
probably the weirdest thing about my installation is that most of my home directory was copied from my previous arch install
because the only thing i can think of is some permission issue
me too, but i've deleted everything that has weird permissions and it seems that files still get recreated with weird permissions
is there a group i'm supposed to be in?
nope
i did see some mention of 524288 being how the container's root uid would appear on the host, is that right?
the problematic dir is owned by uid/gid 524288
thats the correct uid and gid for them
hmm
any podman/distrobox config files that might be lingering from previous install and making them behave badly?
anything mutable would be in your home folder and /etc
btw i did figure this out! the issue was that somehow my home directory was owned by gid 1001, which doesn't seem to be a real group on my system. my primary group has gid 1000. all the subdirectories on my home directory are owned by the right group, but i guess that was still messing with podman.
https://github.com/containers/crun/issues/1483 this issue was what made me check for that
GitHub
Cannot run any container if storage location is owned by a group th...
Running a container in rootless mode with podman fails if a parent directory is owned by a group that is not owned by the user or by the users main group. For example, if the username is user with ...