4 ms·
> it's the streamlining of application deployment. I always liked the idea of nicely integrating with the environment and utilizing the features of package man
by zx2c4 13y ago
> it's the streamlining of application deployment.
I always liked the idea of nicely integrating with the environment and utilizing the features of package managers, the file system, users, and all the rest of the niceties we have at our disposal. "I don't know how to organize a bunch of things together!" seems like a silly reason to containerize every component into a separate root fs.
But on the other hand, I can imagine this work flow does have some merit, and some folks save a lot of time and energy and potential headaches just popping things in containers.
- shykes 13y ago> "I don't know how to organize a bunch of things together!" seems like a silly reason to containerize every component into a separate root fs. One good reason to separate every component is that it facilitates moving them to separate machines down the road, or scaling them separately. Another good reason is that it reduces the out-of-band requirements of the components. "all the niceties" you have at your disposal may very well be specific to your distro, or your site setup. By contrast, docker containers only require docker, which is a single binary file. A developer needs to know his component will run anywhere, not just on your particular setup.