Distrobox stuck at starting container

Hi all, I'm using bazzite-deck-nvidia image and in desktop mode I'm stuck with distrobox while starting a fedora container, precisely at nvidia integration step. It's been like this for at least 10 minutes. Is it a known issue? rpm-ostree status output:
State: idle
Deployments:
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-nvidia:stable
Digest: sha256:f73a274b19d71a51ad8126b91ebce9d22d26d4344c74ff27e99b25f6db84061a
Version: 41.20250106.3 (2025-01-07T04:27:20Z)
Diff: 1 added
LayeredPackages: chntpw

● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-nvidia:stable
Digest: sha256:f73a274b19d71a51ad8126b91ebce9d22d26d4344c74ff27e99b25f6db84061a
Version: 41.20250106.3 (2025-01-07T04:27:20Z)
InterruptedLiveCommit: f8fc69d7c6dce5461f55bb8a5a536f3be4df3a90b451fc089fb6ff8f32c56c12
Unlocked: transient

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-nvidia:stable
Digest: sha256:0f61b2e23fe333e70b6d4ce8c70b985aecc86b4fe93938d8976b697f8e1706f8
Version: 41.20250106.1 (2025-01-06T14:17:32Z)
State: idle
Deployments:
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-nvidia:stable
Digest: sha256:f73a274b19d71a51ad8126b91ebce9d22d26d4344c74ff27e99b25f6db84061a
Version: 41.20250106.3 (2025-01-07T04:27:20Z)
Diff: 1 added
LayeredPackages: chntpw

● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-nvidia:stable
Digest: sha256:f73a274b19d71a51ad8126b91ebce9d22d26d4344c74ff27e99b25f6db84061a
Version: 41.20250106.3 (2025-01-07T04:27:20Z)
InterruptedLiveCommit: f8fc69d7c6dce5461f55bb8a5a536f3be4df3a90b451fc089fb6ff8f32c56c12
Unlocked: transient

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-nvidia:stable
Digest: sha256:0f61b2e23fe333e70b6d4ce8c70b985aecc86b4fe93938d8976b697f8e1706f8
Version: 41.20250106.1 (2025-01-06T14:17:32Z)
hardware: CPU: AMD Ryzen 7 5700X 8-Core Processor GPU: NVIDIA GeForce RTX 3070/PCIe/SSE2 MOBO: Gigabyte Technology Co., Ltd. AB350-Gaming RAM: 16GB
No description
Solution:
I solved running a ujust update manually and then trying again opening a distrobox fedora container
Jump to solution
1 Reply
Solution
Gabry
Gabry4w ago
I solved running a ujust update manually and then trying again opening a distrobox fedora container

Did you find this page helpful?