Re:What's new in Docker 1.13: prune, secrets, checkpoints an...
by scanr on Tuesday January 31, 2017 @07:58AM
(#13530117)
Docker may be overkill to start but it's relatively low cost to implement and it will definitely pay dividends over time:
[ Parent
| on HN ]
Re:What's new in Docker 1.13: prune, secrets, checkpoints an...
by MrBuddyCasino on Tuesday January 31, 2017 @11:52AM
(#13532362)
> it's relatively low cost to implement
Running Docker in production takes a huge amount of effort to get right and is not easily done.
Re:What's new in Docker 1.13: prune, secrets, checkpoints an...
by tra3 on Tuesday January 31, 2017 @01:18PM
(#13533465)
I dont believe that's an accurate assessment. If the grandparent wants to run a one off container with reproducible results, something like docker-compose is perfect. If he wants to run a multi-node microservices architecture then the story gets more complicated.
Re:What's new in Docker 1.13: prune, secrets, checkpoints an...
by LeanderK on Tuesday January 31, 2017 @02:41PM
(#13534441)
i run a lot of small projects with docker-compose on a single host and it makes deploying my changes very easy. Maybe there is a low cost setting it up, but i think eve with a small project it pays it divides pretty fast.
Re:What's new in Docker 1.13: prune, secrets, checkpoints an...
by scanr on Wednesday February 01, 2017 @09:51AM
(#13541112)
I could have been clearer. I meant that setting up docker for his use case i.e. a single 'standard' web application, is relatively easy. Especially if you're using something like Amazon Elastic Beanstalk. At least, that's been my experience.
You're right that docker can become very complex e.g. dockerizing and orchestrating mariadb with galera for high availability was not pleasant.
Re:What's new in Docker 1.13: prune, secrets, checkpoints an...
by MrBuddyCasino on Wednesday February 01, 2017 @10:30AM
(#13541428)
I agree that its actually ok for that use case. But then you don't have a big initial pain to solve, anyway - people using Docker in production usually have few other choices due to the scale they are operating at, and Nomad+Ansible doesn't cut it because there are complex dependencies.