hi - we have a failing deployment which shows stuc...
# ask-for-helpo
Oded Valtzer
04/28/2025, 8:24 PMhi - we have a failing deployment which shows stuck in a CrashLoopBackOff - redeploy don't work either, and we can't see anything bad in the logs... how can we debug this?
d
Dennis Torres
04/28/2025, 8:27 PMWe’re seeing this too @Joseph Obeid
Dennis Torres
04/28/2025, 8:27 PMhovering over the failed status shows a disk space error
o
Oded Valtzer
04/28/2025, 8:28 PMwe see this
Copy code
Back-off restarting failed container main in pod <...>Oded Valtzer
04/28/2025, 8:31 PMthis is the last log we have from this:
Copy code
2025-04-27T17:47:25+0000 [INFO] [:1] Service instance cleanup finalizedj
Joseph Obeid
04/28/2025, 8:37 PMThe status seems to change between what @Oded Valtzer is seeing alone and also including the disk space error:
Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: open /dev/ptmx: no space left on device: unknownJoseph Obeid
04/29/2025, 12:15 AMSeems to have been resolved.
j
Jian Shen Yap
04/29/2025, 2:06 AMHello guys, this has been resolved!
o
Oded Valtzer
04/29/2025, 8:03 AMthanks @Jian Shen Yap - could you elaborate on what happened, and if we could have somehow deal with this ourserlves \ get some sort of alert, see logs?
was kinda in the dark on this for a few hours and couldn't understand if it's a Bento issue or our config\deployment issue. thanks