Distrobox containers can't be accessed due to "OCI permission denied"

Created container with:
distrobox-create --unshare-netns --image ghcr.io/ublue-os/bazzite-arch --name bazzite-arch -Y
distrobox-create --unshare-netns --image ghcr.io/ublue-os/bazzite-arch --name bazzite-arch -Y
Trying to enter with either distrobox-enter bazzite-arch, prompted with:
Error: unable to start container "4c040e8cb21e746e4e71652de358cec5e7c1c862e78cb7eed9e080358a5f1420": crun: open `/var/home/smolkitten/.local/share/containers/storage/overlay/411460099cdaed8999ac318cde8a0bc00f1d58f0f4c83d87de224b39fd31dba5/merged`: Permission denied: OCI permission denied
Error: unable to start container "4c040e8cb21e746e4e71652de358cec5e7c1c862e78cb7eed9e080358a5f1420": crun: open `/var/home/smolkitten/.local/share/containers/storage/overlay/411460099cdaed8999ac318cde8a0bc00f1d58f0f4c83d87de224b39fd31dba5/merged`: Permission denied: OCI permission denied
Yes, I've tried to chown it to myself, chmod g+rwx and o+rwx, still can't access the container. Also happens with all other kinds of images, not just ublue's.
Solution:
Solved. I migrated my home folder from a non-atomic installation and the groupid for $HOME (not the files) was not identical to what I have on the ostree installation for some reason. Applied sudo chown -R smolkitten:smolkitten $HOME and my Distrobox containers now work
Jump to solution
1 Reply
Solution
smolkitten
smolkitten2w ago
Solved. I migrated my home folder from a non-atomic installation and the groupid for $HOME (not the files) was not identical to what I have on the ostree installation for some reason. Applied sudo chown -R smolkitten:smolkitten $HOME and my Distrobox containers now work

Did you find this page helpful?