3 ms·
There's one thing I don't understand well about docker: I saw people making Graphite containers and the like, but won't all data be erased when you close the co
by StavrosK 13y ago
There's one thing I don't understand well about docker: I saw people making Graphite containers and the like, but won't all data be erased when you close the container? It seems to me that any sort of persistent data storage on docker is very inconvenient.
- buro9 13y agoBut 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).
- StavrosK 13y ago> 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.
- LoonyPandora 13y agoIt's new in 0.5.0 [1] - Released ~10 days ago. Things in docker-land move super quick! [1] https://github.com/dotcloud/docker/wiki/Docker-0.5.0:-external-volumes,-advanced-networking,-self-hosted-registry#externally-mounted-volumes https://github.com/dotcloud/docker/wiki/Docker-0.5.0:-extern...
- StavrosK 13y agoOh, very nice, thanks!
- buro9 13y agoAh, 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.
- StavrosK 13y agoYeah, 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.
- dsissitka 13y ago> ...but won't all data be erased when you close the container? No, containers aren't ephemeral: $ docker run -i -t base /bin/bash root@d675bee3cbdb:/# echo 'Hello, world!' > /foo root@d675bee3cbdb:/# exit $ docker restart d675bee3cbdb d675bee3cbdb $ docker attach d675bee3cbdb root@d675bee3cbdb:/# cat /foo Hello, world! root@d675bee3cbdb:/#
- StavrosK 13y agoWeird, they were for me. I guess I was probably starting the base image again? Where do you get the modified id from?
- dsissitka 13y ago> Weird, they were for me. Were you using volumes? Currently a container's volumes are reset when the container is restarted. That's fixed in master. > Where do you get the modified id from? In this case I just copied it from the container's command prompt. It's also available via docker ps -a: $ docker run base sleep 1 $ docker ps -a ID IMAGE COMMAND CREATED STATUS PORTS 041d889d7bd8 base:latest sleep 1 5 seconds ago Exit 0 $
- StavrosK 13y agoHmm, no, I wasn't using volumes. I was doing "docker ps", but didn't notice (or didn't know to use) an id, so I just did "docker run Ubuntu etc".
- StavrosK 13y agoApparently I don't know how to use docker. You are right, I was just starting the base image every time. Starting it creates a new container which you can find with "ps -a", and you can start/attach to it later the way you said. Thanks for the tip, I need to find a good tutorial or write one.