File

mod_posix: Move POSIX signal handling into util.startup to avoid race When libunbound is initialized, it spawns a thread to work in. In case a module initializes libunbound, e.g. by triggering a s2s connection, Prosody would not handle signals, instead immediately quit on e.g. the reload (SIGHUP) signal. Likely because the libunbound thread would not have inherited the signal mask from the main Prosody thread. Thanks Menel, riau and franck-x for reporting and help narrowing down

#!/bin/sh -eux

tag="testing"

if [ "$#" -gt 0 ]; then
	tag="$1"
	shift
fi

containerify="$(command -v podman docker)"

$containerify run -it --rm \
	-v "$PWD:$PWD" \
	-w "$PWD" \
	-v "$HOME/.cache:$PWD/.cache" \
	--entrypoint /bin/bash \
	--userns=keep-id \
	--network \
	host "prosody.im/build-env:$tag" "$@"