container create: signal: killed?
Hey all, I have a task stuck at the booting state, and this is the error message I got:
2024-05-16T18:41:04Z create container stevenynie/dreamweaver:20240516111003
2024-05-16T18:42:04Z error creating container: container: create: container create: signal: killed
2024-05-16T18:42:24Z create container stevenynie/dreamweaver:20240516111003
request_id: 70ca2fc5-bcdf-4819-b936-742a5ed739e6-u1
Any hints on how to avoid this error? It has been like this for 3 mins.
6 Replies
it seems to stuck in a loop, I have to kill it after 5 mins
Another one
2024-05-16T19:56:19Z error starting: Error response from daemon: Container bfa614eb55302822c5d9b0b3d2789589d197d9519f31d24ecb954f5bad10c296 is not paused
2024-05-16T19:57:25Z stop container
2024-05-16T19:57:26Z remove container
2024-05-16T19:57:26Z remove network
7e55d6b1-8553-4fee-a139-676f0f41cc93-u1
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
it's all custom
I also have a custom template, but it just worked for like 50 jobs in a row on different other workers. getting the same restart loop on one worker. don't even know how to debug. if it just died, would have been much better because it'd be a couple minutes of delay. but it's preventing other workers from starting because it's in the "Running" state
also, this specific worker just processed 4 other jobs successfully
That's weird, now I am afraid to try Serverless with Queue based workers as well. Load Balancer is already in Beta and having certain issues🐧