3 ms·
Flatpak is great for self contained apps, but it seems problematic when it has to reach outside the sandbox. I ran into this in VSCode and with CUDA video proce
by brucethemoose2 4y ago
Flatpak is great for self contained apps, but it seems problematic when it has to reach outside the sandbox. I ran into this in VSCode and with CUDA video processing filters, but I'm sure there are more examples.
And thats what distro packages are for, I guess.
- sirius87 4y agoTry using Flatseal [1] which is a Flatpak app that helps manage permissions for other Flatpak apps. You can see exactly what permissions are enabled in each app's sandbox and expand/override everything from env vars to filesystem locations you want to enable access to. [1] https://github.com/tchx84/Flatseal https://github.com/tchx84/Flatseal
- brucethemoose2 4y agoYeah, but "install this thing to manually tweak that thing to get those things to work" is so linux, and is exactly what Flatpak is trying to avoid. On the other hand, its a security issue, so I supposed some opt in friction is prudent.
- sirius87 4y agoFlatseal is only a convenience. I think you'll find that the flatpak CLI [1] has commands to do everything Flatseal does, albeit in an arguably unwieldy way. [1] https://docs.flatpak.org/en/latest/flatpak-command-reference.html#flatpak-permission-set https://docs.flatpak.org/en/latest/flatpak-command-reference...
- AnIdiotOnTheNet 4y agoThere are still things Flatseal cannot make work though. For instance, the Wireshark FlatPak is incapable of actually capturing packets.
- FengLengshun 4y agoYeah, which is why a lot of people in immutable distro uses distrobox. And now, it seems, Nix as well.