Deployment Failed - container event container died
I see that someone else reported a similar issue yesterday, but didn't want to pollute that thread.
My deployment fails with a message of
container event container died and no other helpful logs.
This seems like it can happen at different points during the deploy process, but the deployment never succeeds.
Project ID: 0930ece2-3c15-47d4-b0e3-888db1490b35
Service ID: 5f622eee-800e-4813-a1ff-e8cbc9126713
11 Replies
Project ID:
0930ece2-3c15-47d4-b0e3-888db1490b35,5f622eee-800e-4813-a1ff-e8cbc9126713the container based logs are completely normal and very much expected but only when they are printed at the end of the build logs.
at first glace this looks like the build ran out of memory during the linting and crashed.
will get back to you after i know more!
can i ask you to disable the v2 builder if possible?
I'll try that
@sina @that_one_nerdy tagging teammates for visibility
seems to be failing again with
legacy but a bit differently.. just while taking snapshot
looks like you are still on the v2 builder?
I changed to legacy and hit deploy and these are the logs from that build...
right but the runtime is a separate system from the builder, i had asked you to try disabling the new builder
oh sorry, slightly confusing because 'v2' only appears in the runtime section. you want me to 'disable new builder environment'... will try that
yes, my bad, mixed up my terms
ok yes the build seemed to work with the new builder disabled, thanks!
no problem
will pass that info to the team