nextcloud-cronjob/scripts/healthcheck.sh

#!/usr/bin/env bash
set -x

# Make sure cron daemon is still running
# shellcheck disable=SC2009
ps -o comm | grep crond || exit 1

# Make sure the target container is still running/available
docker inspect -f '{{.State.Running}}' "$(/find-container.sh)" | grep true || exit 1
Initial implementation of the nextcloud cronjob docker image 2018-12-02 02:08:31 +01:00			`#!/usr/bin/env bash`
			`set -x`

			`# Make sure cron daemon is still running`
ci: fix linter errors: healthcheck.sh 2023-11-09 09:04:49 +01:00			`# shellcheck disable=SC2009`
Initial implementation of the nextcloud cronjob docker image 2018-12-02 02:08:31 +01:00			`ps -o comm \| grep crond \|\| exit 1`

			`# Make sure the target container is still running/available`
Cronjob works now between Nextcloud container recreation If the Nextcloud container is recreated while the cronjob container is still running, the ID of the container is obtained each time the cron tasks are executed. Previously it was cached on entrypoint, so if the ID changed this container would fail. 2019-06-21 02:15:55 +02:00			`docker inspect -f '{{.State.Running}}' "$(/find-container.sh)" \| grep true \|\| exit 1`