Initializing empty repo (new feature?)

[uuf6429]

I ran a new container with these variables: RESTIC_REPOSITORY, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, RESTIC_PASSWORD and no cmd set.

This means that (from what I understood), it will just run supervisord and eventually launch the backups.

The first time it tried to do the backup, it failed because restic couldn't find a valid repository.
I had to create another container with the same variables but with the cmd restic init (if I remember correctly).

So, first question: is this normal expected behaviour?
Second question: maybe we can make it into a feature to init the repo if there isn't one (before cron backup)?

[johansmitsnl]

It is normal behaviour. You can spin up the container and run the necessary commands.

You can also check the readme: https://github.com/johansmitsnl/docker-restic#commands-to-start-with

Can you provide a PR to verify and create if no exists or pass a small script to check this?