![]() Mostly this is useful for navigating the snapshots I realize individual paths can be restored with a standard restic run on my Mac once known, but once the repository is mounted, might as well just use it. ![]() $ docker exec -it restic cp /restic/hosts/>/latest/> /dropbox This is an example in “production” I’d create a dedicated keypair and only expose those to the container.įinally, I can use Docker’s exec command to explore the mounted snapshots and copy files into the drop-box: $ docker exec -it restic ls -a /restic/hosts//latest/> ssh directory into a Docker container is a bad idea. ![]() ![]() $ docker run -it -rm -v /Users/>/.ssh:/root/.ssh -v /Users/>/restic/dropbox:/dropbox -e RESTIC_PASSWORD -e RESTIC_REPOSITORY -name restic -cap-add SYS_ADMIN -device /dev/fuse daaave/restic restic mount /resticĪside: Yes, I realize passing one’s entire. The RESTIC_REPOSITORY and RESTIC_PASSWORD environment variables come from a. It passes through /dev/fuse and grants SYS_ADMIN capability, and sends 2 volumes through to the container: ssh keys and a “drop box” to put restored files into. Then I use plain-vanilla Docker (without Compose) to spin up a container that mounts the repository. RUN apk update
0 Comments
Leave a Reply. |