4 ms·
> the sysadmin doesn't need to learn how the container was built just to manage services or deploy new instances I disagree on that point. Just taking a docke
by gerbilly 7y ago
> the sysadmin doesn't need to learn how the container was built just to manage services or deploy new instances
I disagree on that point.
Just taking a docker image from a developer and deploying that to production does not work to well in my experience, and guess who gets the support calls when things break?
If a sysadmin gets a say in how the container images are configured, it usually works out much better.
Also partitioning the filesystem to avoid dependency clashes used to be more important when I used rack mounted servers. Now it's easy enough to deploy separate cloud instances to partition things. And it's a real VM with real tools on it so I can diagnose problems if they arise.
- acdha 7y ago> Just taking a docker image from a developer and deploying that to production does not work to well in my experience, and guess who gets the support calls when things break? In my experience, that's been about the same for any mode of deployment by a developer without ops experience. The main thing Docker added was standardizing the mechanics and avoiding certain classes of errors like not having reproducible builds or deploying local artifacts inconsistently.