Getting started with Docker Running containers Managing containers Managing images Building images Docker swarm mode Docker Data Volumes Debugging a container Inspecting a running container Docker Machine Dockerfiles Docker network Data Volumes and Data Containers Docker Engine API Multiple processes in one container instance Docker Registry Checkpoint and Restore Containers Docker stats all running containers Concept of Docker Volumes Docker events Restricting container network access run consul in docker 1.12 swarm Dockerfile contents ordering docker inspect getting various fields for key:value and elements of list passing secret data to a running container Connecting Containers Logging Creating a service with persistence Docker in Docker security How to debug when docker build fails Docker private/secure registry with API v2 Running Simple Node.js Application Running services Iptables with Docker Docker --net modes (bridge, hots, mapped container and none).How to Setup Three Node Mongo Replica using Docker Image and Provisioned using Chef

Concept of Docker Volumes

Remarks:

People new to Docker often don't realize that Docker filesystems are temporary by default. If you start up a Docker image you'll get a container that on the surface behaves much like a virtual machine. You can create, modify, and delete files. However, unlike a virtual machine, if you stop the container and start it up again, all your changes will be lost -- any files you previously deleted will now be back, and any new files or edits you made won't be present.

Volumes in docker containers allow for persistent data, and for sharing host-machine data inside a container.

A) Launch a container with a volume

[root@localhost ~]# docker run -it -v  /data  --name=vol3   8251da35e7a7 /bin/bash
root@d87bf9607836:/# cd /data/
root@d87bf9607836:/data# touch abc{1..10}
root@d87bf9607836:/data# ls

abc1 abc10 abc2 abc3 abc4 abc5 abc6 abc7 abc8 abc9

B) Now press [cont +P+Q] to move out from container without terminating the container checking for container that is running

[root@localhost ~]# docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d87bf9607836 8251da35e7a7 "/bin/bash" About a minute ago Up 31 seconds vol3 [root@localhost ~]#

C) Run 'docker inspect' to check out more info about the volume

[root@localhost ~]# docker inspect  d87bf9607836

"Mounts": [ { "Name": "cdf78fbf79a7c9363948e133abe4c572734cd788c95d36edea0448094ec9121c", "Source": "/var/lib/docker/volumes/cdf78fbf79a7c9363948e133abe4c572734cd788c95d36edea0448094ec9121c/_data", "Destination": "/data", "Driver": "local", "Mode": "", "RW": true

D) You can attach a running containers volume to another containers

[root@localhost ~]# docker run -it  --volumes-from  vol3  8251da35e7a7  /bin/bash

root@ef2f5cc545be:/# ls

bin boot data dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var

root@ef2f5cc545be:/# ls /data abc1 abc10 abc2 abc3 abc4 abc5 abc6 abc7 abc8 abc9

E) You can also mount you base directory inside container

[root@localhost ~]# docker run -it  -v  /etc:/etc1 8251da35e7a7 /bin/bash

Here: /etc is host machine directory and /etc1 is the target inside container

Contributors

Topic Id: 5908

Example Ids: 20749,20750,20751,20752,20753

This site is not affiliated with any of the contributors.