From fe251a9996367847c5a44a3e9ae8e02baf559826 Mon Sep 17 00:00:00 2001 From: Simon L Date: Thu, 1 Dec 2022 16:29:23 +0100 Subject: [PATCH] add a hint what to do if the backup container was forcefully killed Signed-off-by: Simon L --- Containers/postgresql/start.sh | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Containers/postgresql/start.sh b/Containers/postgresql/start.sh index b2e25a1b..fae1cce4 100644 --- a/Containers/postgresql/start.sh +++ b/Containers/postgresql/start.sh @@ -9,6 +9,8 @@ export PGPASSWORD="$POSTGRES_PASSWORD" # Don't start database as long as backup is running while [ -f "$DUMP_DIR/backup-is-running" ]; do echo "Waiting for backup container to finish..." + echo "If this is incorrect because the backup container is not running anymore (because it was forcefully killed), you might delete the lock file which is by default stored here:" + echo "/var/lib/docker/volumes/nextcloud_aio_database_dump/_data/backup-is-running" sleep 10 done