Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker daemon crashes #92

Closed
2 of 3 tasks
jcassee opened this issue Aug 30, 2017 · 8 comments
Closed
2 of 3 tasks

Docker daemon crashes #92

jcassee opened this issue Aug 30, 2017 · 8 comments

Comments

@jcassee
Copy link

jcassee commented Aug 30, 2017

  • This is a bug report
  • This is a feature request
  • I searched existing issues before opening this one

Expected behavior

Docker does not crash. :-)

Actual behavior

Docker crashes and is restarted by systemd.

Log output quite long, so added as attachment.

Steps to reproduce the behavior

Not sure what caused the crash. Was running docker stack deploy, but that has worked well in the past.

Output of docker version:

Client:
 Version:      17.07.0-ce
 API version:  1.31
 Go version:   go1.8.3
 Git commit:   8784753
 Built:        Tue Aug 29 17:42:53 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.07.0-ce
 API version:  1.31 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   8784753
 Built:        Tue Aug 29 17:41:43 2017
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:

Containers: 6
 Running: 0
 Paused: 0
 Stopped: 6
Images: 15
Server Version: 17.07.0-ce
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: locked
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 3addd840653146c90a254301d6c3a663c7fd6429
runc version: 2d41c047c83e09a6d61d464906feb2a2f3c52aa4
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.12.0-041200-generic
Operating System: Ubuntu 16.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.95GiB
Name: cluster-do-01
ID: BJJ2:RNXD:MNSS:S2ZE:NSJ3:IUVO:RBDC:67AH:G7EQ:IWLJ:GKAK:KOMD
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Username: goaboutansible
Registry: https://index.docker.io/v1/
Labels:
 storage=ssd
 hosting=do
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.)

Digital Ocean droplet, Ubuntu 16.04, kernel 4.12.0-041200-generic #201707022031

@jcassee
Copy link
Author

jcassee commented Aug 30, 2017

Docker also crashed on a similar machine running on a virtual machine at Hetzner.

Log

Client:
 Version:      17.07.0-ce
 API version:  1.31
 Go version:   go1.8.3
 Git commit:   8784753
 Built:        Tue Aug 29 17:42:53 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.07.0-ce
 API version:  1.31 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   8784753
 Built:        Tue Aug 29 17:41:43 2017
 OS/Arch:      linux/amd64
 Experimental: false
Containers: 6
 Running: 3
 Paused: 0
 Stopped: 3
Images: 8
Server Version: 17.07.0-ce
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: active
 NodeID: tw8j61y5rg3e2w3xohk3frsy8
 Is Manager: true
 ClusterID: kore89vpypvecw7eci5irb5ma
 Managers: 5
 Nodes: 20
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
  Force Rotate: 0
 Root Rotation In Progress: false
 Node Address: 78.47.50.4
 Manager Addresses:
  178.62.204.152:2377
  45.77.61.163:2377
  78.47.50.4:2377
  [2a01:4f8:c0c:1e25::2]:2377
  [2a03:b0c0:2:d0::23b1:c001]:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 3addd840653146c90a254301d6c3a663c7fd6429
runc version: 2d41c047c83e09a6d61d464906feb2a2f3c52aa4
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.12.0-041200-generic
Operating System: Ubuntu 16.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.95GiB
Name: cluster-hetzner-02
ID: ETI4:5RUR:WUGI:W62H:WCEF:WC22:KE4G:BH34:PP36:3VB3:2GOW:ILZ3
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
 storage=hdd
 hosting=hetzner
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

Ubuntu 16.04, kernel 4.12.0-041200-generic #201707022031

@cpuguy83
Copy link
Collaborator

Thanks, looks like this is fixed on master with this chunk of code:

moby/moby@b642b3f#diff-f06ce8e825525a9e55c84c084759dd01R31
From moby/moby#34174

@jcassee
Copy link
Author

jcassee commented Aug 31, 2017

Okay, looks like this issue can be closed. I'll drop down to 17.6.1 until that change is released.

@jcassee jcassee closed this as completed Aug 31, 2017
@cpuguy83
Copy link
Collaborator

Thanks! I've opened an internal backports request.

@jcassee
Copy link
Author

jcassee commented Aug 31, 2017

Leaving the issue closed, but this crash is occurring multiple times per day now on Docker 17.06.1-ce / Ubuntu 16.04.

@jcassee
Copy link
Author

jcassee commented Sep 6, 2017

@cpuguy83 Did the change you pointed to get backported into v17.06.2-ce that was just released?

@seemethere
Copy link

@jcassee No unfortunately it did not, here's the tracking PR for that: docker/docker-ce#215

@jcassee
Copy link
Author

jcassee commented Sep 7, 2017

@seemethere Thanks for the link. I subscribe to the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants