Skip to content

Start gunicorn without its control socket - #191

Merged
olsonjp merged 1 commit into
mainfrom
gunicorn-no-control-socket
Nov 10, 2026
Merged

olsonjp merged 1 commit into
mainfrom
gunicorn-no-control-socket

Conversation

@olsonjp

@olsonjp olsonjp commented Nov 10, 2026

Copy link
Copy Markdown
Owner

What

Every container start logs:

`[ERROR] Control server error: [Errno 13] Permission denied: '/home/krill'`

gunicorn 26 (pulled in by the dependency update) opens a control socket under the user's home directory by default. The container runs as the `krill` system user created with `useradd -r`, which has no home directory, so the socket cannot be created. Serving requests is not affected, but the error fires on every start.

Nothing uses the control interface (`gunicornc`), so the fix is `--no-control-socket` in the Dockerfile `CMD` and in `app.yaml`'s `run_command`. The deployment docs mention it.

Verified

  • `gunicorn --no-control-socket --check-config krill.wsgi:application` accepts the flag on gunicorn 26.2.0.
  • `docker build --check .` is clean.
  • Not yet confirmed in a running container: after deploying, the error line should be gone from the startup log.

🤖 Generated with Claude Code

gunicorn 26 opens a control socket under the user's home directory by
default. The container's krill user has no home directory (useradd -r), so
every start logged 'Control server error: Permission denied: /home/krill'.
Nothing here uses the control interface, so turn it off.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@olsonjp
olsonjp merged commit c5116a2 into main Nov 10, 2026
1 check passed
@olsonjp
olsonjp deleted the gunicorn-no-control-socket branch November 10, 2026 03:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant