Hangs upon exit from a container in interactive mode

Docker Desktop for Mac
1

Expected behavior

Does not hang.

Actual behavior

Hangs.

Information

$ pinata diagnose -u
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta8.2
Running diagnostic tests:
[OK]      docker-cli
[OK]      Moby booted
[OK]      driver.amd64-linux
[OK]      vmnetd
[OK]      osxfs
[OK]      db
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Docker logs are being collected into /tmp/20160422-002920.tar.gz
Most specific failure is: No error was detected
Your unique id is: AB265AB8-FA11-4B4E-B89B-2AD2FE3D7B3E
  • OSX 10.11.4

Steps to reproduce the behavior

$ docker pull ubuntu:latest
latest: Pulling from library/ubuntu
759d6771041e: Pull complete
8836b825667b: Pull complete
c2f5e51744e6: Pull complete
a3ed95caeb02: Pull complete
Digest: sha256:b4dbab2d8029edddfe494f42183de20b7e2e871a424ff16ffe7b15a31f102536
Status: Downloaded newer image for ubuntu:latest
$ docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
$ docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
ubuntu              latest              b72889fa879c        8 days ago          188 MB
$ docker run -i -t ubuntu bash
root@d4db19b3a503:/# ls
bin  boot  dev  etc  home  lib  lib64  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
root@d4db19b3a503:/# exit

Hangs here. Ctrl+C and Ctrl+\ do not work. I had to kill the running docker process and it gave me the prompt back. This is reproducible.

1 Like
2

I second report by Aravind SV:

Same OS X build and same Docker.app build. I was testing Alpine distro:

REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
alpine              3.3                 d7a513a663c1        3 weeks ago         4.798 MB
alpinist            latest              d7a513a663c1        3 weeks ago         4.798 MB

Ran the image with docker run --rm -t -i alpinist, whereas alpinist image is the same as alpine 3.3. I would also point out, that docker ps is completely unresponsive.

Restarting the docker.app fixes docker ps, but docker ps -a doesn’t work (but that’s a different error).