I really like: daemontools + static binary + setuidgid and maybe chroot.
Or mesos where everything needs to be in a tarball, which is extracted and sole program run.
If stuff is statically linked and related files (config, assets, ...) are part of bundle that can be chrooted, what is the value add of a container?
It's not hard to use control groups in daemontools family style, either.
* http://jdebp.eu./Softwares/nosh/guide/move-to-control-group....
Re:WTF is a container?
by brazzledazzle on Monday October 17, 2016 @11:25AM
(#12725831)
Containers are easier for folks with less operational experience to understand. Or maybe easier to get started with is a better way to put it. It's easy to underestimate easy to use tooling when you aren't the target demographic.
Did anybody have better experience with e.g. Rkt?