stack/docker/server
Bilal Godil 0b3a9cfacc fix sentinel marker path in docker/server entrypoint
The docker/server image runs as the unprivileged `node` user, which
cannot write to /var/run. With `set -e` at the top of the script, the
failed `touch` aborted execution after sentinel replacement but before
the backend/dashboard were started — the Check server health CI step
then saw connection refused on ports 8101/8102.

Move the marker into $WORK_DIR (which is already created and owned by
the running user). The emulator snapshot-resume path still benefits: the
marker persists across supervisorctl restarts because $WORK_DIR lives
on the container filesystem.
2026-04-15 14:07:34 -07:00
..
.env Turnstile integration for fraud protection (#1239) 2026-03-20 21:26:45 +00:00
.env.example clickhouse setup (#1032) 2026-01-28 09:12:33 -08:00
Dockerfile Fix Docker build 2026-03-09 10:49:42 -07:00
entrypoint.sh fix sentinel marker path in docker/server entrypoint 2026-04-15 14:07:34 -07:00