The linux way to handle it is with a chroot. Used to do this back in the day to get 32bit libraries on a 64bit distro that didn’t include 32bit libraries. chroot is the basis for modern containerization technologies. These days, I usually use it for bleeding edge application builds that don’t have a build for my distro, yet. Distrobox makes it pretty simple. With distrobox, you can install the application you need in the OS that supports the application you want, then just map the binary into your OS.
Same concept. Flatpak is based on bubblewrap, which was based off another tool that was based on chroot.
Edit: Looks like Flatpak is working towards adopting a different (newer) feature that allows some containerization features at the user level, without requiring chroot super user level.
The linux way to handle it is with a
chroot. Used to do this back in the day to get 32bit libraries on a 64bit distro that didn’t include 32bit libraries.chrootis the basis for modern containerization technologies. These days, I usually use it for bleeding edge application builds that don’t have a build for my distro, yet. Distrobox makes it pretty simple. With distrobox, you can install the application you need in the OS that supports the application you want, then just map the binary into your OS.See here: https://distrobox.it/useful_tips/#export-to-the-host
Just fyi containers use
pivot_rootnotchrootI’m aware. I said, “basis”, not “uses”.
Isn’t that functionally what a flatpak is?
Same concept. Flatpak is based on bubblewrap, which was based off another tool that was based on chroot.
Edit: Looks like Flatpak is working towards adopting a different (newer) feature that allows some containerization features at the user level, without requiring chroot super user level.