Container not functional on secondary user

[thehost12]

Hey! I am using a new Bazzite install through the offline ISO, and everything worked relatively well. The only issue is I made a second user, and it cant use Distrobox

Here is the error message:

[unseen919@fedora ~]$ distrobox enter bazzite-arch 
Container bazzite-arch is not running.
Starting container bazzite-arch
run this command to follow along:

 podman logs -f bazzite-arch

Error: OCI runtime error: unable to start container "11cdc0a6a2a912e7288d20fb2563d524e997dbdafb6ab0fdd5ce48d70bc6e022": crun: error executing hook `/usr/bin/nvidia-container-runtime-hook` (exit code: 1)

[spawnedc]

I'm having the same problem. Here's the output of distrobox enter bazzite-arch --verbose (truncated)

DEBU[0000] /usr/bin/conmon messages will be logged to syslog 
DEBU[0000] running conmon: /usr/bin/conmon               args="[--api-version 1 -c e374268d6a0f07c537da37142ff8f1932a3265bfac5bae7a48b742b1ac46d23c -u e374268d6a0f07c537da37142ff8f1932a3265bfac5bae7a48b742b1ac46d23c -r /usr/bin/crun -b /home/canyilmaz/.local/share/containers/storage/overlay-containers/e374268d6a0f07c537da37142ff8f1932a3265bfac5bae7a48b742b1ac46d23c/userdata -p /run/user/1000/containers/overlay-containers/e374268d6a0f07c537da37142ff8f1932a3265bfac5bae7a48b742b1ac46d23c/userdata/pidfile -n bazzite-arch --exit-dir /run/user/1000/libpod/tmp/exits --full-attach -s -l journald --log-level debug --syslog --conmon-pidfile /run/user/1000/containers/overlay-containers/e374268d6a0f07c537da37142ff8f1932a3265bfac5bae7a48b742b1ac46d23c/userdata/conmon.pid --exit-command /usr/bin/podman --exit-command-arg --root --exit-command-arg /home/canyilmaz/.local/share/containers/storage --exit-command-arg --runroot --exit-command-arg /run/user/1000/containers --exit-command-arg --log-level --exit-command-arg debug --exit-command-arg --cgroup-manager --exit-command-arg systemd --exit-command-arg --tmpdir --exit-command-arg /run/user/1000/libpod/tmp --exit-command-arg --network-config-dir --exit-command-arg  --exit-command-arg --network-backend --exit-command-arg netavark --exit-command-arg --volumepath --exit-command-arg /home/canyilmaz/.local/share/containers/storage/volumes --exit-command-arg --db-backend --exit-command-arg boltdb --exit-command-arg --transient-store=false --exit-command-arg --runtime --exit-command-arg crun --exit-command-arg --storage-driver --exit-command-arg overlay --exit-command-arg --events-backend --exit-command-arg journald --exit-command-arg --syslog --exit-command-arg container --exit-command-arg cleanup --exit-command-arg e374268d6a0f07c537da37142ff8f1932a3265bfac5bae7a48b742b1ac46d23c]"
[conmon:d]: failed to write to /proc/self/oom_score_adj: Permission denied

DEBU[0000] Received: -1                                 
DEBU[0000] Cleaning up container e374268d6a0f07c537da37142ff8f1932a3265bfac5bae7a48b742b1ac46d23c 
DEBU[0000] Network is already cleaned up, skipping...   
DEBU[0000] Unmounted container "e374268d6a0f07c537da37142ff8f1932a3265bfac5bae7a48b742b1ac46d23c" 
Error: unable to start container "e374268d6a0f07c537da37142ff8f1932a3265bfac5bae7a48b742b1ac46d23c": crun: [conmon:d]: failed to write to /proc/self/oom_score_adj: Permission denied

create keyring `e374268d6a0f07c537da37142ff8f1932a3265bfac5bae7a48b742b1ac46d23c`: Disk quota exceeded: OCI permission denied
DEBU[0000] Shutting down engines

For some reason, it can not write to /proc/self/oom_score_adj

[Aquis7]

I have tried this and it worked as planned:

distrobox create --name steam3 --image ghcr.io/ublue-os/bazzite-arch:latest

So the arch version worked.

[spawnedc]

Thanks for trying this. To give a little bit more context, I'm using bazzite-nvidia. bazzite-arch was installed right after the installation and when I tried to run it, it worked fine. The problem starts after the first reboot after installing bazzite-arch. I tried removing and re-creating it, but didn't work.

[Aquis7]

OK I found what the problem was with my setup. When I disable SELinux (boot selinux=0) then it fails but when I dont disable SELinux then the world is good.

[Gyromancer]

Thanks for trying this. To give a little bit more context, I'm using bazzite-nvidia. bazzite-arch was installed right after the installation and when I tried to run it, it worked fine. The problem starts after the first reboot after installing bazzite-arch. I tried removing and re-creating it, but didn't work.

I'm also running bazzite-nvidia and am experiencing the same behavior. The bazzite-arch container ran fine on first install, but I can longer enter the container since the first reboot. This problem doesn't seem to be specific to the bazzite-arch container. I created a Fedora 38 distrobox container, and it ran fine until I rebooted. It now errors out in the same way as the bazzite-arch container.

The weird thing about all this is that I get different errors at different times when I run distrobox enter bazzite-arch. Sometimes it says "Disk quota exceeded" despite my drive having plenty of space and running the command from the main admin user. I've also found that I can't enter toolbox containers either. toolbox enter fedora-toolbox-38 --verbose returns

.config/containers/toolbox.conf not found

[Gyromancer]

Okay, I think I found the issue. There's a known bug with podman 4.6.2. There's an impending fix merged in this PR, but podman 4.6.3 is yet to be released. For now, there's a workaround in the issue linked above, though it doesn't seem to be possible on bazzite.