A couple of recent posts here have been all about starting the process of dockerizing/containerizing node applications, which inspired me to play around a bit with Docker yesterday.So, it seems like sticking a node app in docker is pretty straightforward as long as you can follow the Dockerfile templates online. But what you seem to get is a process running in a container that does the same thing as if you had just typed npm start from your development computer.Then there's whatever else your node app depends on which really gets into the weeds. You can create a docker-compose file which launches your local app along with a dockerized database, but there are a lot of articles arguing against dockerized databases, at least in production.It does seem like docker files would help do automated testing in something like CI/CD, but those tools add a ton of configuration to projects. It doesn't seem like docker makes deployment to production much easier without incorporating some CI/CD tool.Is docker most useful for large teams/corporate settings? I'm developing an app solo, and maybe that's why I don't see the win.Anyways, online communities seem to love Docker, so I figure I'm just not understanding, yet, what problems it solves. Can anyone help me understand what I'm missing?
Submitted May 01, 2018 at 06:39PM by aust1nz
No comments:
Post a Comment