From 78e3a1f14543afb363e039d2f5a3017d417b6167 Mon Sep 17 00:00:00 2001 From: andig Date: Mon, 9 Nov 2026 16:43:31 +0100 Subject: [PATCH] fix: disable the gunicorn control socket Co-Authored-By: Claude Opus 5.5 --- Dockerfile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Dockerfile b/Dockerfile index af9eee893..65d0c096d 100644 --- a/Dockerfile +++ b/Dockerfile @@ -53,6 +53,7 @@ ENV OPTIMIZER_TIME_LIMIT=10 ENV OPTIMIZER_NUM_THREADS=1 # the access log is the only source of per request latency, keep the format lean. # the config module reaps solvers left behind by a killed worker, see gunicorn_conf.py -ENV GUNICORN_CMD_ARGS="--workers 4 --max-requests 32 --config python:optimizer.gunicorn_conf --access-logfile - --access-logformat '%(m)s %(U)s %(s)s %(D)s'" +# the control socket would go to the missing home of the app user and nothing uses it +ENV GUNICORN_CMD_ARGS="--workers 4 --max-requests 32 --no-control-socket --config python:optimizer.gunicorn_conf --access-logfile - --access-logformat '%(m)s %(U)s %(s)s %(D)s'" USER app CMD ["/app/.venv/bin/gunicorn", "--bind", "0.0.0.0:7050", "optimizer.app:app"]