Nix might have been removed. I’ll have to check, but I feel like the ujust command forv setting up nix went away a version or two ago.
But I think you can set distroboxes to run at startup, so you’d never know the difference when it came time to actually launch the program. Right (correct me if I’m wrong)?
Maybe, I do not use bazzite and cannot check. But it used to be a feature. You can, of cause, start distrobox at startup, but literally running almost two operation systems might not be the best for performance and RAM usage.
Fortunately, it does not usually cause high load, but it still exists. The only thing I can recomend here is to always check if the dependencies of any package you install in container require to run in the background and avoid those which do.
Nix might have been removed. I’ll have to check, but I feel like the
ujustcommand forv setting upnixwent away a version or two ago.But I think you can set distroboxes to run at startup, so you’d never know the difference when it came time to actually launch the program. Right (correct me if I’m wrong)?
Maybe, I do not use bazzite and cannot check. But it used to be a feature. You can, of cause, start distrobox at startup, but literally running almost two operation systems might not be the best for performance and RAM usage.
Could be a case for
toolbox, which I admittedly know even less about. Either way, people here have offered several options to try!Toolbox is effectively the same thing as distrobox. It is a linux distro inside docker-like container. They even use the same images.
Are there any processes in particular that I should keep an eye on? At the moment I don’t notice any new particularly high load.
Fortunately, it does not usually cause high load, but it still exists. The only thing I can recomend here is to always check if the dependencies of any package you install in container require to run in the background and avoid those which do.