feat(docker): add GUNICORN_LOGLEVEL env var #24308
Merged
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.
SUMMARY
to debug gunicorn, it is useful to specify the log level. This env var gives the possibility to define it in the docker image
TESTING INSTRUCTIONS
in the docker sub directory, run this to build and run the new container:
docker build -t test . && docker run --name test -e GUNICORN_LOGLEVEL=debug -it test
after the build logs, you will see that gunicorn logs now way more verbose than when running with the the
-e GUNICORN_LOGLEVEL=debug
flag.ADDITIONAL INFORMATION