I try to do the same. All vnlib related packages are bundled so they can be run identically from the terminal or inside a container. Gotta have containers though. Deploying user-facing services in running "directly" on a production cluster is not an option imo. Containers remove my reliance on the developer to setup my environment. I can override file paths with mounts, control networking, map uids, dns overrides, scale up and down, migrate easily between machines, and update or roll back by changing the image hash in a single file. I can also force limitations (cgroup stuff) like cpu scheduling, memory limits and whatnot. Nasty things that applications (especially foss apps) usually do that can ruin a shared server.

Replies (1)

yeah, shit programmers is the reason you need containers. i have had to reinstall linux many times in my life because of those shit programmers, when i accidentally clobber some system dependency deep in the stack while trying to build some piece of shit experimental app that does some neat thing. my app is designed like it is a normal user app. if it is found to break other things in the system, it has to be fixed. a lot of server devs don't have that user-first policy like i do. everything must be simple enough that anyone with basic unix shell skills can use it.