What happened?
After running devpod up, container is created but during "devpod agent setup" it fails with exit status 137

What did you expect to happen instead?
Agent setup finished and workspace is available to connect

How can we reproduce the bug? (as minimally and precisely as possible)

I'm using the try-node repo

devpod up github.com/microsoft/vscode-remote-try-node --ide none --debug

Local Environment:

• DevPod Version: v0.6.15
• Operating System: linux (ubuntu 22.04)
• ARCH of the OS: AMD64

DevPod Provider:

• Local/remote provider: docker and ssh (both fail)

Anything else we need to know?
After it fails, if i connect to the container (docker exec -it {container} bash) and run the agent command from debug logs, binary also fails with status 137. If i restart the container (docker restart {container}) the error is not happening again.

I had this bug on another machine, so i just recreated it from scratch, installed ubuntu, docker and devpod. I have around 20gb+ free ram, a lot of disk space and cpu is not being used.

I think it may be related to something else, maybe some docker engine configuration or hardware, but i don't know how to debug it further.

debug logs

devpodlogs.txt