3 ms·
> This would be a lot more compelling if it included testimonials from actual projects bitten by any of the arguments against docker. Disclaimer: I am not affi
by user5994461 10y ago
> This would be a lot more compelling if it included testimonials from actual projects bitten by any of the arguments against docker.
Disclaimer: I am not affiliated with the author. I just experience endless issues with docker in production. Enough to write a book. (just testing future audience for the book)
That, I can provide in a separate blog post! :D
What selection of bugs would you be interested in?
- Critical linux kernel bugs killing the host when running docker
- Containers crashing and corrupting all data on the mounted directories [from the host drive]
- Worldwide outage of docker.com killing all CI pipeline in the world for 7 hours straight
- More critical linux kernel bugs destroying the docker host
- Major breaking changes in docker and docker API (usually between all minor versions), breaking all existing stuff
- Randomly dropping critical features, distribution and filesystem support (to the point where there is actually NO filesystem supported by Docker on some distribution. No kidding xD)
- Various DNS fuckups (special issues on Ubuntu)
- No build-in commands to free disk space of old containers/images (this one is major hassle)
- codezero 10y agoAwesome, you _should_ write a blog post if you have time :) I'm particularly interested in what you did to get around all the bullet points. Are you still using Docker, with some bandaids, or did you move to something different?
- user5994461 10y agoHope you're still here. Comments and feedback welcome. https://thehftguy.wordpress.com/2016/11/01/docker-in-production-an-history-of-failure/ https://thehftguy.wordpress.com/2016/11/01/docker-in-product...
- codezero 10y agoThanks :)