Docker exiting with status code 139

Question

I have a .Net Core application what it to run on a docker image. I typed in the command line :

docker run -d --net=bridge -it --name=testapp -v /var/test/:/var/test microsoft/aspnetcore-build /bin/bash -c "dotnet /var/test/test.dll"

it is created but it is exiting with a status code 139. What could be the problem.

Look [here](https://stackoverflow.com/a/35410993/21567): `139` is essentially the running program inside the container failing with Signal 11, which is a segmentation fault `SIGSEGV`. Test your code outside the container, or run it inside with a debugger attached. There are multiple ways to do the later (google ".net core debug inside container" for a list of options). — Christian.K, Oct 13 '17 at 09:07

score 4 · Accepted Answer · edited Nov 04 '21 at 21:31

4

Instead of running the docker image and running the bash command (-c "dotnet /var/test/test.dll") at the same time, divide it to steps.

For example:

run this command:
```
docker run -d --net=bridge -it --name=testapp -v /var/test/:/var/test microsoft/aspnetcore-build
```
it will run an aspnetcore Image named testapp and map the test file between the your machine and the docker machine.
enter the docker machine:
```
 docker exec -it testapp bash
```
enter the /var/test folder and run the app:
```
 dotnet test.dll
```

edited Nov 04 '21 at 21:31

Nick Jones

answered Nov 21 '17 at 13:23

sam saleh

The run won't work either if the container process crashes right off. – Ain Tohvri Apr 18 '22 at 19:43

score -3 · Answer 2 · answered Jul 27 '18 at 11:45

-3

I fixed Docker error 139 in my project by adding a COPY line before my RUN line in Dockerfile:

COPY blueprint/src/main/python/setup.py setup.py
RUN python setup.py

answered Jul 27 '18 at 11:45

Cees Timmerman

2 Answers2