moby: docker attach hangs 1.11.1 release (experimental)

docker attach operation hangs if, docker daemon in killed and started again. Rest of operations like docker exec and docker ps works fine.

Output of docker version:

$ docker version
Client:
 Version:      1.12.0-dev
 API version:  1.24
 Go version:   go1.5.4
 Git commit:   e3079b4-unsupported
 Built:        Sun May 22 10:18:12 2016
 OS/Arch:      linux/amd64
 Experimental: true

Server:
 Version:      1.12.0-dev
 API version:  1.24
 Go version:   go1.5.4
 Git commit:   e3079b4-unsupported
 Built:        Sun May 22 10:18:12 2016
 OS/Arch:      linux/amd64
 Experimental: true

Output of docker info:

$ docker info
Containers: 18
 Running: 1
 Paused: 0
 Stopped: 17
Images: 68
Server Version: 1.12.0-dev
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 130
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: host bridge null
Kernel Version: 4.4.0-22-generic
Operating System: Ubuntu 16.04 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.796 GiB
Name: dev
ID: 7DLO:3SES:XAM2:QKUY:B5IJ:QABX:3TFB:UE65:6OAE:4CAJ:Y6TG:ML5M
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Experimental: true
Insecure Registries:
 127.0.0.0/8

Working environment in Virtualbox

Steps to reproduce the issue:

  1. Create container in background docker run -itd --name nyan supertest2014/nyan
  2. Check attach operations docker attach nyan
  3. detach from container Ctrl+p + Crtl+q
  4. kill docker daemon using kill -9 $DockerDaemonPID
  5. restart docker daemon systemctl start docker
  6. Try docker ps - successfull
  7. Try docker exec nyan ps
  8. Try docker attach nyan - Hang!!

This issue is always reproducable with 1.11.1 main release and experimental release both.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 16 (16 by maintainers)

Most upvoted comments

@krasi-georgiev No, this scenario is different then you mentioned.

From docker v1.12, docker containers run independently of docker-daemon & docker-daemon can be restarted without affecting container lifecycle.

ref:

Interestingly, now while verifying, I forgot to add --live-restore flag to docker-daemon, which enable daemon to reconnect to running containers after restart.

So this bug is fixed 😃, Closing.