Hi,
This can be closed as resolved.
It turns out the the Gitlab CI environment creates its own entrypoint (/bin/sh) rather than using the container’s built entrypoint; and so in our case caddy was not already running.
1 Like