But if you are putting something like a database in a Docker container, wouldn't you point the storage of the data files at something a little more permanent?
And for everything else that is just data processing in the stack, ephemeral storage isn't a bad thing (stops developers writing things to disk when they shouldn't).
> But if you are putting something like a database in a Docker container, wouldn't you point the storage of the data files at something a little more permanent?
Of course, but how? Can a docker container somehow write to the host fs? It couldn't, a few weeks ago.
Ah, you see this is what I haven't yet done... but I figured you'd just mount some network attached storage and use that for the data files.
Which may or may not be the host machine, and most likely would be the machine you configure to be next door with more focus on SSDs than CPU.
I also figured, but haven't checked, that Docker will eventually support Vagrant-style shared folders. But maybe this breaks the philosophical design of a container.
Yeah, but that's for production. For staging/dev machines it's not very convenient, and I really don't like special-casing things all the time depending on where I have to deploy... It adds a lot of complexity.
As LoonyPandora said below, apparently they added shared folders recently, so I'll play with that today.
And for everything else that is just data processing in the stack, ephemeral storage isn't a bad thing (stops developers writing things to disk when they shouldn't).