`uv run` spawns another process.

[pkucmus]

In the documentation uv run hello.py is used as an example (or the main way) on how to run a project. This assigns the PID 1 to uv and whatever uv spawns is another process - this is problematic when using Docker and need to send signals to your application, like sending SIGHUP, SIGTTIN, SIGTTOU to your container to inform Uvicorn to do something. Docker will only send the signals to the process sunning under PID 1 (here it's explained better then I ever could).

If the UV process can proxy all signals then I guess that would be fine but still I would not be too keen on running a different process in front of my web server, not for the reason of dependency management.

Might be related to: #7342 if uv could install into a non-virtual env (container's only Python)

[zanieb]

You can easily bypass uv run in this context, with one of:

• UV_PROJECT_ENVIRONMENT: https://docs.astral.sh/uv/concepts/projects/#configuring-the-project-environment-path
• Adding the bin/ to the PATH: https://docs.astral.sh/uv/guides/integration/docker/#using-the-environment
• Specifying the full path to your application, e.g., ./.venv/bin/foo
• Activating the environment via the shell

There's some active discussion about signal handling in #6738

[pkucmus]

My main concern of running the web server as the PID 1 process can be solved with the points you mentioned and I'll move the rest of the discussion into #6738.