prosody-docker/entrypoint.sh

#!/bin/bash -e
set -e

data_dir_owner="$(stat -c %u "/var/lib/prosody/")"
if [[ "$(id -u prosody)" != "$data_dir_owner" ]]; then
    usermod -u "$data_dir_owner" prosody
fi
if [[ "$(stat -c %u /var/run/prosody/)" != "$data_dir_owner" ]]; then
    chown "$data_dir_owner" /var/run/prosody/
fi

if [[ "$1" != "prosody" ]]; then
    exec prosodyctl "$@"
    exit 0;
fi

if [[ "$LOCAL" && "$PASSWORD" && "$DOMAIN" ]]; then
    prosodyctl register "$LOCAL" "$DOMAIN" "$PASSWORD"
fi

exec setpriv --reuid=prosody --regid=prosody --init-groups "$@"
Fix minor shellcheck warnings 2021-01-16 15:33:16 +00:00			`#!/bin/bash -e`
Cleanup the Dockerfile - Reduce the build steps to reduce the number and size of intermediate images - Set the logging to stdout by default - Remove default user create, but still allow optional user creation - Fix entrypoint command setup 2014-12-08 02:59:37 +00:00			`set -e`

Fix mod_posix error if prosody user ID was altered This fixes the following mod_posix error: Couldn't write pidfile at /var/run/prosody/prosody.pid; /var/run/prosody/prosody.pid: Permission denied 2021-01-16 15:28:34 +00:00			`data_dir_owner="$(stat -c %u "/var/lib/prosody/")"`
			`if [[ "$(id -u prosody)" != "$data_dir_owner" ]]; then`
			`usermod -u "$data_dir_owner" prosody`
			`fi`
			`if [[ "$(stat -c %u /var/run/prosody/)" != "$data_dir_owner" ]]; then`
			`chown "$data_dir_owner" /var/run/prosody/`
			`fi`
Run with same UID as datadir owner This should fix problems with owner/uid mismatch when an existing prosody data directory is mounted into the container Closes #39 2020-02-13 00:10:36 +00:00
entrypoint.sh: If a command is passed to the image, run prosodyctl instead 2016-02-04 19:19:17 +00:00			`if [[ "$1" != "prosody" ]]; then`
Revert "Use tini as PID 1 inside the container" This reverts commit 31d6d84433e13390b770e7ff6c430f1652ce90bd. While tini successfully forwards signals, this leads to `runuser` killing prosody now. The container does terminate in 10 seconds, so Docker is happy and you could argue that actually fixes #68, but it's no graceful shutdown. The revert is done because it's easier to apply a real fix without tini. 2021-03-21 19:16:33 +00:00			`exec prosodyctl "$@"`
entrypoint.sh: If a command is passed to the image, run prosodyctl instead 2016-02-04 19:19:17 +00:00			`exit 0;`
			`fi`

Fix minor shellcheck warnings 2021-01-16 15:33:16 +00:00			`if [[ "$LOCAL" && "$PASSWORD" && "$DOMAIN" ]]; then`
entrypoint.sh: Quote variables [shellcheck] 2019-03-16 18:19:37 +00:00			`prosodyctl register "$LOCAL" "$DOMAIN" "$PASSWORD"`
Cleanup the Dockerfile - Reduce the build steps to reduce the number and size of intermediate images - Set the logging to stdout by default - Remove default user create, but still allow optional user creation - Fix entrypoint command setup 2014-12-08 02:59:37 +00:00			`fi`

Fix signal handling and allow graceful shutdown Although cc88073a798d ("Fix signal handling") fixed the signal handling and signals don't end up in `entrypoint.sh` anymore, there's still no clean graceful shutdown. The reason is runuser. It runs as PID 1 and prosody only runs as child process. A SIGTERM sent to runuser lets runuser forward SIGTERM to the child process. However it does not wait, but send SIGKILL right after it. (Confirmed by looking at runuser source code in util-linux.) The output on `docker stop [prosodycontainer]` is therefore: Session terminated, killing shell...mod_posix warn Received SIGTERM portmanager info Deactivated service 'c2s' ...killed. The additional messages in between prosody log output come from runuser. This is obviously no graceful shutdown. Because prosody fordibs running as uid 0 (root) we have to run it as unpriviledged user. The docker best practices recommend to use gosu and gosu lists some alternatives. Instead of installing gosu to the image, we use setpriv from the already installed util-linux now. The version in Debian buster, on which the prosody image is based currently, is recent enough to already contain setpriv. After that, prosody itself runs with PID 1, but as unpriviledged user now, and the output of `docker stop` looks like this: mod_posix warn Received SIGTERM portmanager info Deactivated service 'c2s' general info Shutting down... general info Shutdown status: Cleaning up general info Shutdown complete Link: https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#entrypoint Signed-off-by: Alexander Dahl <post@lespocky.de> 2021-03-21 19:57:07 +00:00			`exec setpriv --reuid=prosody --regid=prosody --init-groups "$@"`