Docker Community Forums

Share and learn in the Docker community.

Docker run -it has started failing with status 139


(Richardthepeace) #1

I’ve been happily using the run command with the -it switch (interactive/allocate pseudo-TTY) forever until this morning, all attempts to run containers in this way have started to fail with status code 139.

What does status code 139 mean here and what might the problem be?

Thanks, Richard.


(Olaf Meeuwissen) #2

Don’t know what the 139 exit status means but I’m seeing the same behaviour since I upgraded the Linux kernel for my Debian GNU/Linux stretch system from linux-image-4.7.0.1-amd64 to linux-image-4.8.0-1.amd64. The odd thing is that this only happens with the official centos:6 and centos:6.8 images. The centos:7 image (and the latest images for debian, ubuntu and fedora) work fine.

I tested with docker-engine 1.12.0 and 1.23.0 using docker run -it <image> /bin/bash.


(Thomasantoniusc) #3

I am the same issue, I hope someone finds a solution soon. I had to switch my host OS to get around it, which I’m not happy about.