Skip to content

Fix gunicorn logging in docker#390

Open
deepanshutiwari27 wants to merge 1 commit into
chaoss:mainfrom
deepanshutiwari27:fix-issue-374
Open

Fix gunicorn logging in docker#390
deepanshutiwari27 wants to merge 1 commit into
chaoss:mainfrom
deepanshutiwari27:fix-issue-374

Conversation

@deepanshutiwari27

@deepanshutiwari27 deepanshutiwari27 commented Jun 13, 2026

Copy link
Copy Markdown

Implemented the Docker Gunicorn logging fix for CollectOSS #374.
Root cause: Docker already relies on gunicorn_conf.py setting errorlog = '-', but both CLI startup paths passed --log-file, which overrides the config and sends Gunicorn errors only to the file. Docker then has nothing useful to show via docker logs.
Changes:
Added internal Gunicorn command builder: collectoss/application/cli/_gunicorn.py (line 17)
Updated backend startup to omit --log-file in Docker: collectoss/application/cli/backend.py (line 108)
Updated API startup the same way: collectoss/application/cli/api.py (line 65)
Switched Gunicorn config to the current Docker env name and kept errorlog = '-': collectoss/api/gunicorn_conf.py (line 45)
Added focused regression tests: tests/test_application/test_cli/test_gunicorn_command.py (line 7)

Fixes #374

Signed-off-by: Deepanshu Tiwari <tiwarideepanshu235@gmail.com>
@MoralCode MoralCode changed the title Fix issue #374 Fix gunicorn logging in docker Jun 14, 2026
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.

gunicorn failures do not log in docker

1 participant