restic snapshots exit code check

[avgeeklucky]

This has caused me problems:

restic-backup-docker/entry.sh

Lines 16 to 31 in a07b831

	restic snapshots &>/dev/null
	status=$?
	echo "Check Repo status $status"
	if [ $status != 0 ]; then
	echo "Restic repository '${RESTIC_REPOSITORY}' does not exists. Running restic init."
	restic init
	init_status=$?
	echo "Repo init status $init_status"
	if [ $init_status != 0 ]; then
	echo "Failed to init the repository: '${RESTIC_REPOSITORY}'"
	exit 1
	fi
	fi

Specifically, I've had backups be interrupted mid process (post backup cleanup or the backup it self, not sure) and they have locked the repository, causing restic snapshots to return a non 0 exit code, next the entry script tries to init a new repository which fails because it's already there. Because I've got restart=always, the container ends up in a restart loop.

I'm not sure how to fix this since restic does not provide meaningful exit codes (restic/restic#956). String parsing is not a great idea either...

[bruno-lopes]

I detected the same problem here. Perhaps it would be nice to use the following command

restic --no-lock list locks

This way it is possible to detect logs and provide a meaningful message to warn the user about the problem.

[niondir]

Sounds good. Feel free to provide a PR.

[wuast94]

have the error too and all my backups cant start anymore :/