190n
190n
PostsComments
UBUniversal Blue
Created by 190n on 12/7/2024 in #🛟bazzite-help
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: 
Error: unable to start container "7180389eef271ab8853481381b363f31cdf839e41ecf787a5586a427f7bea568": crun: open `/var/home/ben/.local/share/containers/storage/overlay/685d29c60873b9b6fb66c58667f333378a385f74b5fb3d61c2944ae747bf8c32/merged`: Permission denied: OCI permission denied
Error: unable to start container "7180389eef271ab8853481381b363f31cdf839e41ecf787a5586a427f7bea568": crun: open `/var/home/ben/.local/share/containers/storage/overlay/685d29c60873b9b6fb66c58667f333378a385f74b5fb3d61c2944ae747bf8c32/merged`: Permission denied: OCI permission denied
The permissions on that directory's parent are: 
$ ls -ld .local/share/containers/storage/overlay/685d29c60873b9b6fb66c58667f333378a385f74b5fb3d61c2944ae747bf8c32/
drwx------. 1 524288 524288 46 Dec  7 13:33 .local/share/containers/storage/overlay/685d29c60873b9b6fb66c58667f333378a385f74b5fb3d61c2944ae747bf8c32/
$ ls -ld .local/share/containers/storage/overlay/685d29c60873b9b6fb66c58667f333378a385f74b5fb3d61c2944ae747bf8c32/
drwx------. 1 524288 524288 46 Dec  7 13:33 .local/share/containers/storage/overlay/685d29c60873b9b6fb66c58667f333378a385f74b5fb3d61c2944ae747bf8c32/
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.
17 replies