distrobox broke (cannot start `/nix`)
I think a recent update broke Distrobox and since then I couldn't access my containers. I've seen other people also has a problem with distrobox, but their fix won't work for my particular case. If anyone has a solution for my particular case, please share it here. Thanks!
20 Replies
My distrobox also just got broken.
Rolling back to my previous deployment has fixed this for now. @RippandT have you tried doing a rollback?
not yet, and I don't even know if I still have an old deployment still in my system
which version did you rollback to?
You should have two images at all times no?
Bazzite-DX 42.20250425
I'll check
I don't have this version in my system. I'll rebase my current stable one to this
it still doesn't work in bazzite:42.20250425
is it a problem with distrobox itself?
I'll rebase back to latest stable
Honestly no clue. I looked at the diff between my two versions and the file causing problems was present
that file is generated when you set a hostname with hostnamectl afaik
if it doesn't exist your nic will give you a random hostname
aka set a hostname
Right. Do you have any idea why distrobox is no longer working between updates then?
its just a breaking changes, remaking the box also work
if I do have some data or installed programs from the nonworking containers, is there still a way to transfer them over to the new one?
sudo touch /etc/hostname will fix it without remaking boxesit doesn't work for me unfortunately
I think it only works when you have the /etc/hostname error
yes that's true
oh i didnt realize its two different issue
people need to avoid hijacking thread ðŸ˜
it's fine! They probs thought that the fix for the hostname error would work with my /nix one
but if I do
sudo touch /nix it will complain that it is a read-only folderyeah the nix one is a bit different
nix itself afaik doesnt really like to run in container
but I wonder why distrobox tries to call for it now, or if it usually does why does it error now?
nix stuff isnt really supported here too
Yeah sorry, if that folder is present the only possible way is if you used the Nix installer
And we can no longer support your install as a result