Repository navigation
Start gunicorn without its control socket - #191
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
🤖 Generated with Claude Code