'Container is not running' issue / bug?
I'm encountering a persistent issue when trying to launch pods, and I'm hoping you can investigate. I'm seeing similar behaviour across different templates and regions.
Pods are failing to reach a stable "Running" state. They have started showing a "container is not running" status shortly after creation. There are no application-specific logs generated. This happens even for templates that were previously working.
What I've Tried:
* Multiple Custom Images: I've tried deploying with several different tags of my custom image
goom1000/comfyui-5090-base:<some-tag>
, including the latest (:v[latest tag]-...
) and older, previously functional tags.
* Known-Good Community/Official Templates: The issue also occurs when attempting to deploy official RunPod templates or other community templates that are known to work.
* Different Regions: I've attempted deployments in multiple regions (including EU-RO-1), with the same result.
* No Volume Attached: The problem persists even when deploying without attaching my persistent storage volume, so it's not volume-related.
* Different GPUs: The issue occurs even when attempting to deploy on RTX 4090 instances, where I previously had a working setup.
Any assistance you can provide would be greatly appreciated.
Thanks!
Solution:Jump to solution
can you check if there is any firewall or extensions that might block requests to runpod's server
3 Replies