[cpuguy83]

Disagree... Also disclaimer, I work at Docker, and particularly spend a large amount of time working on storage for the docker engine.

Volumes are exactly what you should be using to have data that lives beyond the life of the container. Essentially, if you are writing to disk in your container, you should probably be writing it to a volume.

Volumes can be backed by any number of storage solutions, including from every cloud provider, various distributed block, gluster, ceph, etc...

Docker should _not_ be changing the way you run a database. If you need a highly available database, you don't use 1 database process and hope for the best, you use the built-in replication features available in just about every database product in existence today... database goes down, oh well you have a hot-standye ready.