Process running in container stucks in write() to /dev/pts syscall #353
Description
- This is a bug report
- This is a feature request
- I searched existing issues before opening this one
Expected behavior
Process started in docker container prints many lines to stdout in infinit loop, all appears on console where docker client is attached.
Actual behavior
Sometimes process hangs in write() syscall to /dev/pts.
When user press any button in console (where docker client is running) all pipeline continue to work for some time.
Steps to reproduce the behavior
docker run -it --rm busybox:latest base64 /dev/urandom
base64 starts to output data...
wait for several minutes...
output stops. problem
press any button in terminal and output continues.
Reproduced with
17.11.0-ce
17.12.0-ce
18.03.1-ce
18.06.0-ce-rc1
Not reprocudes with
17.09.1-ce
17.10.0-ce
Output of docker version:
Client:
Version: 18.06.0-ce-rc1
API version: 1.38
Go version: go1.10.3
Git commit: 20580f1
Built: Fri Jun 29 12:20:34 2018
OS/Arch: linux/amd64
Experimental: false
Server:
Engine:
Version: 18.06.0-ce-rc1
API version: 1.38 (minimum version 1.12)
Go version: go1.10.3
Git commit: 20580f1
Built: Fri Jun 29 12:19:31 2018
OS/Arch: linux/amd64
Experimental: false
Output of docker info:
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 200
Server Version: 18.06.0-ce-rc1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: cbef57047e900aeb2bafe7a634919bec13f4a2a5
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.13.0-45-generic
Operating System: Ubuntu 16.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.853GiB
Name: sdc
ID: I7D4:62FZ:MSXH:X2JC:RZ35:U4YG:LKXH:DF6F:N6RZ:QP6P:BNVB:A5JS
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Also reproduced on
Client:
Version: 18.03.1-ce
API version: 1.37
Go version: go1.9.5
Git commit: 9ee9f40
Built: Thu Apr 26 07:17:14 2018
OS/Arch: linux/amd64
Experimental: false
Orchestrator: swarm
Server:
Engine:
Version: 18.03.1-ce
API version: 1.37 (minimum version 1.12)
Go version: go1.9.5
Git commit: 9ee9f40
Built: Thu Apr 26 07:15:24 2018
OS/Arch: linux/amd64
Experimental: false
Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 29
Server Version: 18.03.1-ce
Storage Driver: vfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 773c489c9c1b21a6d78b5c538cd395416ec50f88
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: 949e6fa
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.16.0-0.bpo.1-cloud-amd64
Operating System: Debian GNU/Linux 9 (stretch)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.766GiB
Name: docker
ID: PJ5D:6P34:GZTM:MGRV:OHXX:RXUV:MEAB:UU74:TAP5:2VUT:WIJW:YWGB
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false