Reboots? No problem baby! But shutdowns just gets stuck in plymouth for a loong time
Reboots? No problem baby! But shutdowns just gets stuck in plymouth for a loong time
KThat's new, give me a bit and I'll send you a command to run
KTo figure it out
TLearning how to use distrobox. Is there a performance impact when running games through containers?
TOr anything i should be worried about or watch out for?
TAny advice is appreciated
DThere is a minor performance impact, but generally its not noticeable in Distrobox (sadly that's not the case for the steam flatpak thanks to a bug)
TWdym?
TIn all reality I'm not going to be running steam games through distro box
Diirc the steam flatpak (also a container) has a bug that leads to more noticeable performance hits, hence why Bazzite layers it onto the image instead of preinstalling the flatpak
TOh ok
DBut distrobox doesn't have that issue in my experience, so you should get near native performance
TNice
TCompatibility issues, like would anything be buggy or not work?
TI'm running an arch container
DI think you need to install feral gamemode on both the host and the container to use it
DIf you get proton issues, you may need to add the flags used in bazzite-arch, but I think distrobox has patched them now
TIs bazzite arch a container?
D(As in
--unshare-netns)DYeah, its pretty much an arch container with gaming stuff preinstalled, like steam and lutris
TSo would you recommend that instead of just arch
DIt used to be preinstalled in Bazzite, although its no longer recommended since it had some issues, especially on nvidia GPUs
TWell I'm on bazzite-deck
TSo AMD
TSo would you say a normal arch container would be better?
GStick to bazzite-deck and use a normal Arch container for your needs
DNot sure, havent ever used Bazzite-arch outside of nvidia
TThe motivations for this in the first place is that any other package manager other than pacman, yay, flatpak, that I've tried in bazzite has not been a good experience at all for me
TPlan is to first try and see if I can get a flatpak for a program and install on bazzite and if there isn't, I'll install it on the arch container
GJust use whatever container that gives you the software you need, really
TTrue
GIt's recommended to do distrobox > rpm-ostree layering anyway if you can help it
DYep, thats generally the way to go, flatpak first (other than steam), and distroboxes for everything else
TI tried rpm-ostree and it was so slow I wanted to kms
GFlatpaks for GUI, distrobox for CLI and misc software
TAnd I had to restart the deck every time
GYou should only use rpm-ostree for packages that don't play nicely in distrobox (such as VPN software)
GStick to a minimal amount of additional layered packages
DYou can
--apply-live to install software to the live system without rebooting btwTOh cool
TStill would rather avoid using it lol
DBut listen to @Geechan said
GThe reason it takes so long btw is because it's effectively rebuilding your system image each time you layer a new package
DUse it as little as possible
GThat is computationally expensive
DAll I have layered is qemu (and its dependencies) and mullvad
D(Fuck, why does qemu have so many dependencies)
TDoes rpm-ostree automatically install dependencies?
TOr do you have to like figure it out
Doh and also the dependencies for
auto-cpufreqGLikewise. I have QEMU, a language input library, and my shell layered (zsh)
