stack/docker
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
..
backend Backend fallback (cloud run) (#1306) 2026-04-11 00:57:37 +00:00
dependencies pin adobe/s3mock to 4.12.2 to fix CI bucket creation (#1314) 2026-04-08 11:10:05 -07:00
dev-postgres-replica External db sync (#1036) 2026-02-05 12:04:31 -08:00
dev-postgres-with-extensions Sign up rules (#1138) 2026-02-03 11:08:24 -08:00
local-emulator faster snapshot resume via mapped-ram + rotation opt-out 2026-04-15 13:04:15 -07:00
mock-oauth-server Local emulator (#422) 2025-02-13 18:57:02 +01:00
server fix sentinel marker path in docker/server entrypoint 2026-04-15 14:07:34 -07:00