docker is exited immediately when runs with error code 139

Question

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

Sam Worley · Answer 1 · 2022-10-21T11:39:12.467

15

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-

Add the following to .wslconfig in %userprofile%\.wslconfig

[wsl2]
kernelCommandLine = vsyscall=emulate

edited Oct 21 '22 at 11:39

answered Sep 02 '20 at 14:51

Sam Worley

337
2
8

1

thanks @sam-worley, your anwser gave me the right way. Summary: create a file named .wslconfig in the user directory C://users/[your user name]/.wslconfig with content "`[wsl2] kernelCommandLine = vsyscall=emulate`" and restart pc: https://dev.to/damith/docker-desktop-container-crash-with-exit-code-139-on-windows-wsl-fix-438 – Silvan Oct 28 '21 at 06:52

score 11 · Answer 2 · answered Apr 04 '19 at 05:51

11

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.

answered Apr 04 '19 at 05:51

wmorrell

4,988
4
27
37

thanks wmorrell, is any way to log this somewhere the error – arunraj770 Apr 04 '19 at 05:54
4

Run `docker inspect [container ID]` using the container ID found in the `docker ps` output. That will dump a big JSON object containing info about that container, potentially including more information on what caused the termination. Also, `docker logs [container ID]`. – wmorrell Apr 04 '19 at 05:57

score 7 · Answer 3 · answered Oct 29 '21 at 03:49

7

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.

Ref: https://stackoverflow.com/a/35410993/7160815

answered Oct 29 '21 at 03:49

Savindi

123
1
8

score 0 · Answer 4 · edited May 20 '20 at 15:51

0

I faced the same issue while trying to connect to port 1433 from my host to docker (error code 139). I was able to resolve it by using Administrator: Windows Powershell.

edited May 20 '20 at 15:51

double-beep

5,031
17
33
41

answered May 20 '20 at 14:53

Santandar

121
1
3

docker is exited immediately when runs with error code 139

4 Answers4