Persistent Docker Containers
Docker Fundamentals
Docker has become a very popular tool for orchestrating services. Docker it much more lightweight than virtual machines. For instance do containers not require a boot process. Docker follows the philosophy that one container serves only one process. So in contrast to virtual machines which often bundle several services together, Docker is built for running single services per container. If you come from the world of virtualised machines, Docker can be a bit confusing in the beginning, because it uses its own terminology. A good point to start is as always the documentation and there are plenty of great tutorials out there.
Images and Containers
Docker images serves as templates for the containers. As images and containers both have hexadecimal ids they are very easy to confuse. The following example shows step by step how to create a new container based on the Debian image and how to open shell access.
# Create a new docker container based on the debian image
sudo docker create -t --name debian-test debian:stable
# Start the container
sudo docker start debian-test
# Check if the container is running
sudo docker ps -a
# Execute bash to get an interactive shell
sudo docker exec -i -t debian-test bash
A shorter variant of creating and launching a new container is listed below. The run command creates a new container and starts it automatically. Be aware that this creates a new container every time, so assigning a container name helps with not confusing the image with the container. The command run is in particular tricky, as you would expect it to run (i.e. launch) a container only. In fact, it creates a new one and starts it.
sudo docker run -it --name debian-test debian:stable bash
Important Commands
The following listing shows the most important commands:
# Show container status
sudo docker ps -a
# List available images
sudo docker images
# Start or stop a container
sudo docker start CONTAINERNAME
sudo docker stop CONTAINERNAME
# Delete a container
sudo docker rm CONTAINERNAME
You can of course create your own images, which will not be discussed in this blog post. It is just important to know that you can’t move containers from your host so some other machine directly. You would need to commit the changes made to the image and create a new container based on that image. Please be aware that this does not include the actual data stored in that container! You need to manually export any data and files from the original container and import it in the new container again. This is another trap worth noting. You can, however, also mount data in the image, if the data is available at the host at the time of image creation. Details on data in containers can be found here.
Persisting Data Across Containers
The way how Docker persists data needs getting used to in the beginning, especially as it is easy to confuse images with containers. Remember that Docker images serve only as the template. So when you issue the command sudo docker run … this actually creates a container from an image first and then starts it. So whenever you issue this command again, you will end up with a new container which does share any data with the previously created container.
Docker 1.9 introduced data volume containers, which allow to create dedicated data containers which can be used from several other containers. Data volume containers can be used for persisting data. The following listing shows how to create a data volume container and mount the volume in a container.
# Create a data volume
sudo docker volume create --name data-volume-test
# List all volumes
sudo docker volume ls
# Delete the container
sudo docker rm debian-test
# Create a new container, now with the data volume
sudo docker create -v data-volume-test:/test-data -t --name debian-test debian:stable
# Start the container
sudo docker start debian-test
# Get the shell
sudo docker exec -i -t debian-test bash
After we logged into the shell, we can see the data volume we mounted on the directory test-data:
root@d4ac8c89437f:/# ls -la
total 76
drwxr-xr-x 28 root root 4096 Aug 3 13:11 .
drwxr-xr-x 28 root root 4096 Aug 3 13:11 ..
-rwxr-xr-x 1 root root 0 Aug 3 13:10 .dockerenv
drwxr-xr-x 2 root root 4096 Jul 27 20:03 bin
drwxr-xr-x 2 root root 4096 May 30 04:18 boot
drwxr-xr-x 5 root root 380 Aug 3 13:11 dev
drwxr-xr-x 41 root root 4096 Aug 3 13:10 etc
drwxr-xr-x 2 root root 4096 May 30 04:18 home
drwxr-xr-x 9 root root 4096 Nov 27 2014 lib
drwxr-xr-x 2 root root 4096 Jul 27 20:02 lib64
drwxr-xr-x 2 root root 4096 Jul 27 20:02 media
drwxr-xr-x 2 root root 4096 Jul 27 20:02 mnt
drwxr-xr-x 2 root root 4096 Jul 27 20:02 opt
dr-xr-xr-x 267 root root 0 Aug 3 13:11 proc
drwx------ 2 root root 4096 Jul 27 20:02 root
drwxr-xr-x 3 root root 4096 Jul 27 20:02 run
drwxr-xr-x 2 root root 4096 Jul 27 20:03 sbin
drwxr-xr-x 2 root root 4096 Jul 27 20:02 srv
dr-xr-xr-x 13 root root 0 Aug 3 13:11 sys
drwxr-xr-x 2 root root 4096 Aug 3 08:26 <span style="color: #0000ff;"><strong>test-data</strong></span>
drwxrwxrwt 2 root root 4096 Jul 27 20:03 tmp
drwxr-xr-x 10 root root 4096 Jul 27 20:02 usr
drwxr-xr-x 11 root root 4096 Jul 27 20:02 var```
We can navigate into that folder and create a 100 M data file with random data.
root@d4ac8c89437f:~# cd /test-data/ root@d4ac8c89437f:/test-data# dd if=/dev/urandom of=100M.dat bs=1M count=100 100+0 records in 100+0 records out 104857600 bytes (105 MB) copied, 6.69175 s, 15.7 MB/s root@d4ac8c89437f:/test-data# du -h . 101M .
When we exit the container, we can see the file in the host file system here:
stefan@stefan-desktop:~$ sudo ls -l /var/lib/docker/volumes/data-volume-test/_data insgesamt 102400 -rw-r–r– 1 root root 104857600 Aug 3 15:17 100M.dat```
We can use this volume transparently in the container, but it is not depending on the container itself. So whenever we have to delete to container or want to use the data with a different container, this solution works perfectly. Thw following command shows how we mount the same volume in an Ubuntu container and execute the ls command to show the content of the directory.
stefan@stefan-desktop:~$ sudo docker run -it -v data-volume-test:/test-data-from-debian --name ubuntu-test ubuntu:16.10 ls -l /test-data-from-debian
total 102400
-rw-r--r-- 1 root root 104857600 Aug 3 13:17 100M.dat
You can display a lot of usefil information about a container with the inspect command. It also shows the data container and where it is mounted.
sudo docker inspect ubuntu-test
...
"Mounts": [
{
"Name": "data-volume-test",
"Source": "/var/lib/docker/volumes/data-volume-test/_data",
"Destination": "/test-data-from-debian",
"Driver": "local",
"Mode": "z",
"RW": true,
"Propagation": "rprivate"
}
],
...```
We delete the ubuntu container and create a new one. We then start the container, open a bash session and write some test data into the directory.
stefan@stefan-desktop:~$ sudo docker create -v data-volume-test:/test-data-ubuntu -t –name ubuntu-test ubuntu:16.10 f3893d368e11a32fee9b20079c64494603fc532128179f0c08d10321c8c7a166 stefan@stefan-desktop:~$ sudo docker start ubuntu-test ubuntu-test stefan@stefan-desktop:~$ sudo docker exec -it ubuntu-test bash root@f3893d368e11:/# cd /test-data-ubuntu/ root@f3893d368e11:/test-data-ubuntu# ls 100M.dat root@f3893d368e11:/test-data-ubuntu# touch ubuntu-writes-a-file.txt
When we check the Debian container, we can immediately see the written file, as the volume is transparently mounted.
stefan@stefan-desktop:~$ sudo docker exec -i -t debian-test ls -l /test-data total 102400 -rw-r–r– 1 root root 104857600 Aug 3 13:17 100M.dat -rw-r–r– 1 root root 0 Aug 3 13:42 ubuntu-writes-a-file.txt```
Please be aware that the docker volume is just a regular folder on the file system. Writing from both containers the same file can lead to data corruption. Also remember that you can read and write the volume files directly from the host system.
Backups and Migration
Backing up data is also an important aspect when you use named data volumes as shown above. Currently, there is no way of moving Docker containers or volumes natively to a different host. The intention of Docker is to make the creation and destruction of containers very cheap and easy. So you should not get too attached to your containers, because you can re-create them very fast. This of course is not true for the data stored in volumes. So you need to take care of your data yourself, for instance by creating automated backups like this sudo tar cvfz Backup-data-volume-test.tar.gz /var/lib/docker/volumes/data-volume-test and re-store the data when needed in a new volume. How to backup volumes using a container is described here.