3 ms·
Is that really a problem anymore? Not being able to install things was common in multi-user thin-client type systems, but these days with containerisation and V
by malux85 9y ago
Is that really a problem anymore? Not being able to install things was common in multi-user thin-client type systems, but these days with containerisation and VMs, if you're allowed to execute a script, you're probably allowed to install new packages
No?
- angry_octet 9y agoSadly, no. It is often possible to install things locally, i.e. not using apt. The idea that everyone has sudo privs is unrealistic. A version of apt that added a per user subset would be very useful.
- cyphar 9y agoThis is actually one of the things that made me work on rootless containers (https://rootlesscontaine.rs https://rootlesscontaine.rs). It is a pity that everyone assumes you have sudo access to all of the machines you want to run code on.
- Aissen 9y agoThere are other ways. fakeroot/fakechroot for a poor man's "container" (I cringe inside when I say that). Cross compilation + copying binaries. Or compiling on target with an appropriate ./configure --prefix.
- ymse 9y agoNix and Guix allow unprivileged package operations. I regularly run "one-off" stuff in a `guix environment` that includes all the required packages for that command, without polluting my user (or system) profile. For example, I recently wanted to transfer a file over HTTP from one machine to another, and did not have the "python" executable in PATH. So I started it in a `guix environment` and "containerized" it (using user namespaces) just for show: guix environment --container --network --ad-hoc python -- python3 -m http.server That starts the HTTP server from the current directory, but the process can not see anything else from the "real" system.