From ddc34be55d007c16958e431d254694b3da42d125 Mon Sep 17 00:00:00 2001 From: Fridgemagnet Date: Fri, 4 Feb 2022 11:52:59 +0100 Subject: [PATCH] Updated README.md "Restoring..." section example (#56) Edited the "Restoring a volume from a backup" section example to be able to better differentiate between the names of the temporary restore container and the name of the mounted restore volume. New example container name: temp_restore_container The restore volume name remains the same: backup_restore Also changed "one-off container" to "once-off container". --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index a80843a..120b323 100644 --- a/README.md +++ b/README.md @@ -429,12 +429,12 @@ In case you need to restore a volume from a backup, the most straight forward pr ```console tar -C /tmp -xvf backup.tar.gz ``` -- Using a temporary one-off container, mount the volume (the example assumes it's named `data`) and copy over the backup. Make sure you copy the correct path level (this depends on how you mount your volume into the backup container), you might need to strip some leading elements +- Using a temporary once-off container, mount the volume (the example assumes it's named `data`) and copy over the backup. Make sure you copy the correct path level (this depends on how you mount your volume into the backup container), you might need to strip some leading elements ```console - docker run -d --name backup_restore -v data:/backup_restore alpine - docker cp /tmp/backup/data-backup backup_restore:/backup_restore - docker stop backup_restore - docker rm backup_restore + docker run -d --name temp_restore_container -v data:/backup_restore alpine + docker cp /tmp/backup/data-backup temp_restore_container:/backup_restore + docker stop temp_restore_container + docker rm temp_restore_container ``` - Restart the container(s) that are using the volume