Table of Contents

1. Challenge

   Discover Anonymous Docker Volumes

   1. View the currently available Docker images.
   2. List any existing Docker volumes.
   3. Run two postgres:12.1 containers in detached mode.
   4. Inspect the postgres containers to learn about the attached volumes.
   5. Run another detached postgres container using the --rm flag.
   6. List the Docker volumes, then shut down the postgres containers to see what effect that has on the volumes.
2. Challenge

   Create a Docker Volume

   1. Create a Docker volume for the website code.
   2. Copy the website code into the volume from the host. You will need to use root permissions.
3. Challenge

   Use the Website Volume with Containers

   1. Run an httpd container and mount the data volume. Expose container port 80 to view the website.
   2. View the webpage in a browser. Use the public IP address of your instance.
   3. Run another httpd container using the --rm flag. What do you expect will happen with the data volume when this container is stopped?
   4. List the current Docker volumes.
   5. Stop the temporary httpd container.
   6. List the Docker volumes again. Did the volume behave like you expected?
4. Challenge

   Clean Up Unused Volumes

   1. Remove any volumes not currently in use.
   2. View the new list of volumes.
5. Challenge

   Back Up and Restore the Docker Volume

   1. Inspect the website Docker volume to find its location on disk.
   2. Back up the Docker volume from the host by using tar to create a compressed archive.
   3. Back up the Docker volume from a container by mounting the volume and a backup data location to another container.
   4. Restore a backup.

   Note: Because the Docker data directories are protected, change to the root user for this task using sudo su - and the provided password.