> A slightly smarter .tar.gz would have solved the problem just as well.
It's called "OS package" ;) and can provide more strict sandboxing using a systemd unit file: unit files provide seccomp, cgroups and more.
It's called "OS package" ;) and can provide more strict sandboxing using a systemd unit file: unit files provide seccomp, cgroups and more.
1) is not a containerisation problem. It’s a team problem. I can jam in a load of npm and pip installs in to a shell install script. Maybe even delete /usr/ for the hell of it. Because the script isn’t isolated from the OS I can cause more damage.
This problem is actually solved by doing code reviews properly and team discussions.
2) errr no. Containers != infrastructure. If you want to deploy on bare metal, you can.
Yes, systemd unit files are containers, just like Docker.
Nix tries to solve this, but it isn't there just yet.
Use the same OS and similar hardware for development and production.
Also means developers can work in whatever environment they want, but the result will be reproducible (almost) anywhere.