πž‹΄π›‚π›‹π›†Aug 5, 2023

How do you containerize stuff you install from source in a way that you can completely remove later?

https://lemmy.world/post/2722803

How do you containerize stuff you install from source in a way that you can completely remove later? - Lemmy.world

I’m doing a bunch of AI stuff that needs compiling to try various unrelated apps. I’m making a mess of config files and extras. I’ve been using distrobox and conda. How could I do this better? Chroot? Different user logins for extra home directories? Groups? Most of the packages need access to CUDA and localhost. I would like to keep them out of my main home directory.

Show threadGlomeAug 5, 2023
You can’t completely remove distrobox image and contents later?
Show threadπž‹΄π›‚π›‹π›†Aug 5, 2023
By default it is just the packages and dependencies that are removed. Your /home/user/ directory is still mounted just the same. This puts all of your config and dot files in all the normal places. If you install another distro like Arch on a Fedora base, it also installs all of the extra root package locations for arch and these get left on the host system after removing the distrobox instance. So yeah it still makes a big mess.
Show threadmrh
You can mount any directory you want as the β€œhome” directory of a given container with distrobox, it just defaults to using your home directory.
Aug 6, 2023 at 1:35amWeb
Show threadπž‹΄π›‚π›‹π›†Aug 6, 2023
Do you happen to know what distrobox options there are for extra root directories associated with other distro containers, if there is an effective option to separate these, or if this is part of the remote β€œhome” mount setting? I tried installing an Arch container on a fedora base system. Distrobox automatically built various Arch root directories even though the container should have been rootless.