The docker image is re-built on every deployment using project's /docker/openshift/Dockerfile.
The codebase is built into image's /var/www/html folder using composer: composer install --no-progress --profile --prefer-dist --no-interaction --no-dev --optimize-autoloader as root user.
The container is run as random UID (non-root) user (like uid 10009900) that has no write permissions to any files (except inside /tmp folder), meaning that files inside the container cannot be modified after the image is built.
See City-of-Helsinki/drupal-docker-images for more documentation about the underlying Docker image.
Crons are run inside a separate cron container and use docker/openshift/cron-entrypoint.sh as an entrypoint.
The cron container is run using the same image as the Drupal container and should contain everything your normal container does.
Any scripts placed in repository's docker/openshift/crons folder will be copied automatically to /crons folder inside the cron container. The entrypoint executes all scripts in /crons directory and will die if any of the scripts fail, so that if any of the scripts fail, the whole container exists with a failure. OpenShift automatically restarts failed cron container.
The scripts are not restarted if they exit gracefully, meaning they must be run inside an infinite loop. You can use sleep XX to define how often a certain task should be run.
The cron script must contain something like:
#!/bin/bash
echo "Starting my custom cron script: $(date)"
while true
do
echo "Running my custom cron script: $(date)"
drush my_custom_command
# Sleep for 60 seconds.
sleep 60
doneThe scripts should check any preconditions and exit gracefully if they should not be run in some environments. For example, you can use is_drupal_module_enabled function from docker/openshift/init.sh and exit if required modules are not enabled.
#!/bin/bash
source /init.sh
if ! is_drupal_module_enabled "helfi_react_search"; then
exit 0
fi
...