From d735e9678b73dc946a9538478bead47deaf16d4f Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Tue, 9 Dec 2025 22:47:34 -0700 Subject: [PATCH] Update Scripts/Bash/Transfer Docker Containers.md --- Scripts/Bash/Transfer Docker Containers.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Scripts/Bash/Transfer Docker Containers.md b/Scripts/Bash/Transfer Docker Containers.md index 87192a6..5c2d36d 100644 --- a/Scripts/Bash/Transfer Docker Containers.md +++ b/Scripts/Bash/Transfer Docker Containers.md @@ -38,5 +38,12 @@ On the source (old) server, perform an rsync over to the new server, authenticat rsync -avz -e ssh --progress /srv/containers/example nicole@192.168.3.30:/srv/containers ``` +=== "Quick & Dirty w/ SSH Key Method" + This method assumes that you have the private key for your SSH-based authentication locally on the server somewhere safe with permissions `chmod 600` applied to it. In this example, I placed the private key at `/tmp/id_rsa_OpenSSH`. + + ``` sh + rsync -avz -e "ssh -i /tmp/id_rsa_OpenSSH" --progress /srv/containers/pihole nicole@192.168.3.62:/srv/containers + ``` + ## Spinning Up Docker / Portainer Stack Once everything has been moved over, copy the `docker-compose` and `.env` (environment variables) from the old server to the new one, pointing to the same location since we maintained the same folder structure, and the container should spin up like nothing ever happened. \ No newline at end of file