weird but #distrobox is not in the @VoidLinux repos. tho it's easy to install, i created this simple project to build an xbps package automatically
https://git.ralen.top/ralen/distrobox-xbps/
if you want to uninstall it, you can use uninstall.sh after packaging, tho simple "xbps-remove distrobox" should be enough - the official script does not seem to contain any different logic for removing containers etc
now i can play factorio and windows games from my void installation through distrobox! lutris doesn't work on #void, tho i could manage to run one of my #wine games with void's wine, but other return some wow64 errors and can only be run with prepackaged proton with umo... so i run them from #lutris from distrobox instead.
had to create user services to run #podman as a user, by default it comes with /etc/sv/podman to be linked to /var/services/podman, starting podman as root, so i *copied* the services' scripts to ~/.config/sv and linked to ~/.config/service/, and now podman runs from my user, and i can access it fine with podman-tui
so #runit services are just sets of scripts, basically you need the /var/service/name/run (~/.config/service/name/run) - executable sh script which starts the needed daemon as soon as the file is detected, and /etc/sv (~/.config/sv) is a directory where these scripts are stored
/etc/runit contains scrpts that are run at startup and shutdown, it's easy to create a custom script. for example, i have a script hx /etc/runit/shutdown.d/6-save-backlight.sh which has only 2 lines: mkdir and brightnessctl get > file, and /etc/runit/core-services/12-restore-backlight.sh that set's the brightness with brightnessctl if the file exists. and it just works! #systemd really overcomplicates things, runit is much more intuitive and easy, and everything i need is working just fine
#linuxgaming #voidlinux