I have a web api project with running fine when i ran through visual studio, able to build the image also. but when i run using the command
docker run -d -t -p 8000:83 8fbf296e2173
shows no error and the container will be listed in docker ps -a
with the status
Exited (139) 1 second ago
Please help to solve this
Issue : Docker Container exits on Docker desktop (Windows) with exit code 139. This is a known problem when running Docker desktop with WSL based engine on windows. The culprit is the base OS of your docker image. The Fix is pretty simple. To fix this, You have to Enable vsyscall=emulate in the kernel config to run older base images.
Any error in this can exit the container. So, our Support Engineers check the Dockerfile and correct it. For instance, changing the COPY command to AND command can fix this error. Later we need to start this exited container.
For anyone's future reference; Docker exit code 139 ( 128 + 11) means that a container received a SIGSEGV. This may be a result of invalid memory reference. Show activity on this post. I faced the same issue while trying to connect to port 1433 from my host to docker (error code 139).
As we have said, docker run command launch docker container by reading Dockerfile. Any error in this can exit the container. So, our Support Engineers check the Dockerfile and correct it. For instance, changing the COPY command to AND command can fix this error. Later we need to start this exited container.
It's impossible to say what the root cause is without knowing more about the image that is running. But, the Exited (139)
basically means the PID 1 of the container was sent SIGKILL
. It could be anything, segfault, out of memory, stack overflow, etc.
Started using WSL 2 and encountered the same issue. The workaround posted here has resolved things for me: https://github.com/microsoft/WSL/issues/4694#issuecomment-556095344
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With