I’m using restic inside a kubernetes container, and the script I’m using does a simple repo init (on s3) then backup.
However, if I re-launch the container, it fails when doing the init:
“Fatal: create key in repository at s3:s3.amazonaws.com/ failed: repository master key and config already initialized”
I’m not mounting any volumes on this, so I would expect restic to just “re-attach” to the existing bucket, not fail with a fatal error.
Any thoughts on how I could get it to re-use an existing bucket?