Removing old dummy keys from readme, looks better
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful

This commit is contained in:
Andrew Davidson 2023-07-06 08:30:46 -07:00
parent 1cf7db5336
commit 55c90393db
Signed by: amd
SSH key fingerprint: SHA256:ugJCg4p5ibiMeQwZ9n6ZlhMGEX8uZv/M5q1oeV6BY3Q

View file

@ -15,7 +15,7 @@ Start a container on the backup host with this command:
amdavidson/backup:latest
Add your ssh key to the host:
docker cp id_rsa.pub backup:/bkup/.ssh/authorized_keys
docker run --volumes-from backup amdavidson/backup-server chown 1111:1111 /bkup/.ssh/authorized_keys
@ -36,8 +36,8 @@ On the machine with the container to be backed up, create a repository for backu
--rm \
--volumes-from backup \
--env RESTIC_PASSWORD=secretpw \
--env AWS_ACCESS_KEY_ID=asvc0832n20vasfdh0 \
--env AWS_SECRET_ACCESS_KEY=aokjsvdn0e2nc08va80428b308jcwa08je02983jr032 \
--env AWS_ACCESS_KEY_ID=$ACCESS_KEY \
--env AWS_SECRET_ACCESS_KEY=$SECRET_KEY \
amdavidson/backup-server \
restic -r s3:s3.wasabisys.com/other-container init
@ -48,8 +48,8 @@ Perodically run a backup with a command similar to this:
--volumes-from backup \
--volumes-from other-container:ro \
--env RESTIC_PASSWORD=secretpw \
--env AWS_ACCESS_KEY_ID=asvc0832n20vasfdh0 \
--env AWS_SECRET_ACCESS_KEY=aokjsvdn0e2nc08va80428b308jcwa08je02983jr032 \
--env AWS_ACCESS_KEY_ID=$ACCESS_KEY \
--env AWS_SECRET_ACCESS_KEY=$SECRET_KEY \
amdavidson/backup-server \
restic -r s3:s3.wasabisys.com/other-container backup /data