R
RunPod3mo ago
marcus

Custom image stuck on Initializing with systems logs in loop

All requests are stuck in queue, all workers are stuck in Initializing. The systems logs repeat
2024-03-28T23:57:42Z ghcr.io/company/image@sha256:c7b75238a9e3f3a699eaf2be5e7f86cc260a2d6c9401695bcefc0a953744e82e Pulling from company/image
2024-03-28T23:57:42Z Digest: sha256:c7b75238a9e3f3a699eaf2be5e7f86cc260a2d6c9401695bcefc0a953744e82e
2024-03-28T23:57:42Z Status: Image is up to date for ghcr.io/company/image@sha256:c7b75238a9e3f3a699eaf2be5e7f86cc260a2d6c9401695bcefc0a953744e82e
2024-03-28T23:57:42Z worker is ready
2024-03-28T23:57:42Z ghcr.io/company/image@sha256:c7b75238a9e3f3a699eaf2be5e7f86cc260a2d6c9401695bcefc0a953744e82e Pulling from company/image
2024-03-28T23:57:42Z Digest: sha256:c7b75238a9e3f3a699eaf2be5e7f86cc260a2d6c9401695bcefc0a953744e82e
2024-03-28T23:57:42Z Status: Image is up to date for ghcr.io/company/image@sha256:c7b75238a9e3f3a699eaf2be5e7f86cc260a2d6c9401695bcefc0a953744e82e
2024-03-28T23:57:42Z worker is ready
many many times container logs are
No Container logs yet, this usually means that the pod is still initializing
No Container logs yet, this usually means that the pod is still initializing
2 Replies
marcus
marcus3mo ago
the endpoint id (I think?) is ov1oys3ixlevtc
abtx
abtx3mo ago
Same!