Project: Video_Creation (afa90af7-64a6-49e9-92b4-67e661ee8bf6)

Environment: production (8ce33774-2916-4b39-b637-74bb3c087e45)

Region: US West

Since 2026-09-16 ~11:41 UTC, every deployment of a Dockerfile-based service (python:3.11-slim-bullseye) gets stuck after "Starting Container" — zero log output, no error, no crash, and the deployment eventually settles as "Completed" (instance status EXITED) without ever binding its port.

I isolated this to the container level, not my app code:

• A start command as simple as echo A && python3 -c "print(1)" && echo B prints only "A" — python3 itself never produces output or returns, even after several minutes.
• Reproduced identically on a brand-new service created from scratch (service ID 22408c67-bd1b-47cc-8044-b4becf96c682) with a fresh build, ruling out a corrupted service/image.
• Reproduced with and without a persistent volume attached.
• The build itself always succeeds cleanly (Dockerfile builds fine, image pushes fine).
• Still reproducing as of 2026-09-17.

Deployment IDs to inspect:

• 43f92021-25f9-41d2-8d6a-6cdf77bf3c73
• 55145b0b-3393-4247-ab75-ac9abaaaf68a
• 23fa4a6e-9c97-4411-8cf1-1f03d3e2cf8e (latest, 2026-09-17)

Could you check the underlying compute node/builder for this environment for a possible hang or resource issue affecting Python processes specifically?