You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using uv to run a containerized gunicorn app, it will not pass along SIGTERM to children.
If I install a flask app with pip and run it with gunicorn as the ENTRYPOINT or CMD, it will handle SIGTERM as expected. However, if I use 'uv run', it will hang.
The only difference between the two run command is this:
CMD ["gunicorn", "--config", ...]
vs.
CMD["uv", "run", "gunicorn", "--config", ...]
uv version: uv 0.4.23 (83f835b 2024-10-17)
When using uv to run a containerized gunicorn app, it will not pass along SIGTERM to children.
If I install a flask app with pip and run it with gunicorn as the ENTRYPOINT or CMD, it will handle SIGTERM as expected. However, if I use 'uv run', it will hang.
The only difference between the two run command is this:
CMD ["gunicorn", "--config", ...]
vs.
CMD["uv", "run", "gunicorn", "--config", ...]
http://blog.dscpl.com.au/2015/12/issues-with-running-as-pid-1-in-docker.html
https://petermalmgren.com/signal-handling-docker/
The text was updated successfully, but these errors were encountered: