I've been running Docker in production for a year and both of these issues were very real.
I got bit hard by this issue:
https://github.com/docker/docker/issues/20079
when CoreOS stable channel updated Docker. All my data volume containers broke during the migration and migration could not be reverted.
As for the second issue: when two systemd services that pull containers with the same base images would start simultaneously, they would deadlock pretty reliably. Had to flock every pull as a result. This might be fixed by now though.
Yikes that issue has been open since February?!
Re:Docker not ready for primetime
by sovietmudkipz on Sunday August 28, 2016 @10:52PM
(#12379699)
I'm echoing /u/bogomipz' request for elaboration. I rely heavily on docker-managed data volumes for data. The advice in these threads of comments is alarming. Should I conclude that hackernews devs don't understand docker-managed volumes, or is there some glaringly obvious downside that I'm failing to see?
"you don't use it to store data" - What is wrong with Docker volumes specifically? What issues did you run into?
"wrap docker pulls with 'flock' so they don't deadlock" - I have never had a problem with docker pull, can you elaborate on this?