Monday 15 March 2010

boot2docker - docker commit data container to private registry -



boot2docker - docker commit data container to private registry -

i've tried number of ways , it's still not working. docs have read suggest it's not possible it's bothering me go on dig. here's setup:

i have info container docker build -t databox . docker run -d -v /data -v /data/db --name databox databox (/data , /data/db volumes in databox container i'm sharing) i have test container access info container docker run --volumes-from databox -it --name bbdb busybox /bin/sh i edited file in /data , /data/db directories

now want take snap of databox container, force snap registry, delete local, , restore image had pushed such 2 files edited restored.

my registry server located on 127.0.0.1:5000. here save:

docker tag databox 127.0.0.1:5000/databox:latest docker commit databox 127.0.0.1:5000/databox:latest docker force 127.0.0.1:5000/databox:latest

my restore lools like:

docker run -d -v /data -v /data/db --name databox databox

when perform restore edits have made missing. when @ images , containers along docker history not see edits. have tried edit databox container in different folders , restore original state.

hmmmm.... mean?

what missing how docker info volumes work.

data volumes locations in containers not part of container layered file system. info volumes not part of docker images either. info volumes stored in /var/lib/docker/volumes.

docker commands such export, cp, save, diff or commit have no access info volumes.

the right way backup info docker info volume run docker container having access info volume , run command within container produce archive of data. more info on subject, read docker user guide on managing data.

docker boot2docker

No comments:

Post a Comment