nextcloud-cronjob/scripts/find-container.sh

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

if [[ ! -z "$NEXTCLOUD_PROJECT_NAME" ]]; then
    containerName="${NEXTCLOUD_PROJECT_NAME}[_-]"
    matchEnd="[\._-]\d+"
else
    matchEnd=","
fi

containerName="${containerName}${NEXTCLOUD_CONTAINER_NAME}"

# Get the ID of the container so we can exec something in it later
docker ps --format '{{.Names}},{{.ID}}' | \
    egrep "^${containerName}${matchEnd}" | \
    awk '{split($0,a,","); print a[2]}'
Initial implementation of the nextcloud cronjob docker image 2018-12-02 02:08:31 +01:00			`#!/usr/bin/env bash`
			`set -e`

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			`if [[ ! -z "$NEXTCLOUD_PROJECT_NAME" ]]; then`
Support naming conventions for compose v2 and swarm - Naming convention in Docker Swarm: Fixes #14 - Compose v2 uses `-` separator instead of `_`: Fixes #10 2022-03-19 20:00:38 +01:00			`containerName="${NEXTCLOUD_PROJECT_NAME}[_-]"`
Use correct match ending for project naming mode 2022-03-19 20:15:31 +01:00			`matchEnd="[\._-]\d+"`
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			`else`
Use correct match ending for project naming mode 2022-03-19 20:15:31 +01:00			`matchEnd=","`
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			`fi`
Initial implementation of the nextcloud cronjob docker image 2018-12-02 02:08:31 +01:00
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			`containerName="${containerName}${NEXTCLOUD_CONTAINER_NAME}"`

			`# Get the ID of the container so we can exec something in it later`
Initial implementation of the nextcloud cronjob docker image 2018-12-02 02:08:31 +01:00			`docker ps --format '{{.Names}},{{.ID}}' \| \`
			`egrep "^${containerName}${matchEnd}" \| \`
			`awk '{split($0,a,","); print a[2]}'`