From 517ac59d833d7575d994bf5eb7b2dd953e4bc342 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Thu, 11 Apr 2024 00:04:33 -0600 Subject: [PATCH] Update Scripts/Bash/Transfer Docker Containers.md --- Scripts/Bash/Transfer Docker Containers.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/Scripts/Bash/Transfer Docker Containers.md b/Scripts/Bash/Transfer Docker Containers.md index 9619c82..8c443ca 100644 --- a/Scripts/Bash/Transfer Docker Containers.md +++ b/Scripts/Bash/Transfer Docker Containers.md @@ -2,6 +2,9 @@ If you find that you need to migrate a container, along with any supporting files, permissions, etc from an old server to a new server, rsync helps make this as painless as possible. Be sure to perform the following steps to make sure that you can copy the container's files. +!!! warning + You need to stop the running containers on the old server before copying their data over, otherwise the state of the data may be unstable. Once you have migrated the data, you can spin up the containers on the new server and confirm they work before deleting the data on the old server. + On the destination (new) server, the directory needs to exist and be writable via the person copying the data over SSH: === "Safe Method" @@ -19,10 +22,6 @@ On the destination (new) server, the directory needs to exist and be writable vi sudo chmod 777 /srv/containers ``` - -!!! warning - You need to stop the running containers on the old server before copying their data over, otherwise the state of the data may be unstable. Once you have migrated the data, you can spin up the containers on the new server and confirm they work before deleting the data on the old server. - On the source (old) server, perform an rsync over to the new server, authenticating yourself as you will be prompted to do so: === "Safe Method"