Public bug reported: Original report here: https://github.com/docker/docker/issues/23095. It is copied here in it's entirety. This does not happen with the official docker 1.11.1 package. I did not try with docker's official 1.10.3 package.
This is a patched xenial VM in Azure. Something is happening when I try to stop containers on a 16.04 VM. I lose my ssh session, my tmux session and the machine "soft reboots". `docker version`: ``` Client: Version: 1.10.3 API version: 1.22 Go version: go1.6.1 Git commit: 20f81dd Built: Wed, 20 Apr 2016 14:19:16 -0700 OS/Arch: linux/amd64 Server: Version: 1.10.3 API version: 1.22 Go version: go1.6.1 Git commit: 20f81dd Built: Wed, 20 Apr 2016 14:19:16 -0700 OS/Arch: linux/amd64 ``` `docker info`: ``` Containers: 16 Running: 0 Paused: 0 Stopped: 16 Images: 15 Server Version: 1.10.3 Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: 68 Dirperm1 Supported: true Execution Driver: native-0.2 Logging Driver: json-file 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: 1 Total Memory: 3.359 GiB Name: master ID: KSVP:ECEP:LOQS:3YWO:WBWU:PSK4:5TGO:FSSS:2WYA:6RZM:OVJV:CCS6 WARNING: No swap limit support ``` This is on an Ubuntu 16.04 VM in Azure. **Steps to reproduce the issue:** 1. Use kubelet with cbr0 mode 2. Start some containers 3. Kill those containers **Describe the results you received:** Docker seems to fail to stop the containers. Next in the logs is something indicating that `docker` sent SIGTERM to `systemd-journald`: ``` May 29 22:13:57 master systemd-journald[64414]: Journal stopped May 29 22:13:57 master systemd-journald[2398]: Runtime journal (/run/log/journal/) is 34.4M, max 34.3M, 0B free. May 29 22:13:57 master systemd-journald[64414]: Received SIGTERM from PID 943 (docker). ``` **Additional information you deem important (e.g. issue happens only occasionally):** * [This is `sudo journalctl -f | tee journal.log` right before I deleted the containers](https://gist.githubusercontent.com/anonymous/fe72ad251ad5c6ffa2b5de1d35266def/raw/18d4b65f93fa3b3e0761fb1db4a378ef7d8f2fe6/journal.log). The output stops whenever things go south... so you can correlate with * [The full log journal](https://gist.githubusercontent.com/anonymous/16e84686164eb30106e9be3df7e94183/raw/7be120462ed92464c3328bc81f50fe75f4775c35/journal_full.log) The relevant section: ``` May 29 22:13:56 master kernel: eth0: renamed from vethd82d06e May 29 22:13:56 master kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1386aab: link becomes ready May 29 22:13:56 master kernel: cbr0: port 4(veth1386aab) entered forwarding state May 29 22:13:56 master kernel: cbr0: port 4(veth1386aab) entered forwarding state May 29 22:13:56 master docker[943]: time="2016-05-29T22:13:56.448536888Z" level=warning msg="Error getting v2 registry: Get https://registry-1.docker.io/v2/: dial tcp 52.203.89.113:443: connect: network is unreachable" May 29 22:13:56 master kernel: device veth842eb8f entered promiscuous mode May 29 22:13:56 master kernel: IPv6: ADDRCONF(NETDEV_UP): veth842eb8f: link is not ready May 29 22:13:56 master kernel: cbr0: port 8(veth842eb8f) entered forwarding state May 29 22:13:56 master kernel: cbr0: port 8(veth842eb8f) entered forwarding state May 29 22:13:56 master systemd-udevd[2199]: Could not generate persistent MAC address for veth842eb8f: No such file or directory May 29 22:13:56 master systemd-udevd[2262]: Could not generate persistent MAC address for veth57870ea: No such file or directory May 29 22:13:56 master kernel: device veth1335787 entered promiscuous mode May 29 22:13:56 master systemd-udevd[2264]: Could not generate persistent MAC address for veth1335787: No such file or directory May 29 22:13:56 master kernel: IPv6: ADDRCONF(NETDEV_UP): veth1335787: link is not ready May 29 22:13:56 master kernel: cbr0: port 11(veth1335787) entered forwarding state May 29 22:13:56 master kernel: cbr0: port 11(veth1335787) entered forwarding state May 29 22:13:57 master kernel: cbr0: port 8(veth842eb8f) entered disabled state May 29 22:13:57 master kernel: cbr0: port 11(veth1335787) entered disabled state May 29 22:13:57 master kernel: eth0: renamed from vetheb5efdc May 29 22:13:57 master kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth842eb8f: link becomes ready May 29 22:13:57 master kernel: cbr0: port 8(veth842eb8f) entered forwarding state May 29 22:13:57 master kernel: cbr0: port 8(veth842eb8f) entered forwarding state May 29 22:13:57 master kernel: eth0: renamed from veth57870ea May 29 22:13:57 master kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1335787: link becomes ready May 29 22:13:57 master kernel: cbr0: port 11(veth1335787) entered forwarding state May 29 22:13:57 master kernel: cbr0: port 11(veth1335787) entered forwarding state May 29 22:13:57 master docker[943]: time="2016-05-29T22:13:57.650521456Z" level=info msg="Container 2d77443ef5362361e8102211b85e4663d6f91b5fd49d786dabd7bbabe3f96740 failed to exit within 2 seconds of SIGTERM - using the force" May 29 22:13:57 master docker[943]: time="2016-05-29T22:13:57.651441861Z" level=info msg="Container f41bca579433fd4ba9d63690ba7fb10b468081f541efb569dfabd72daa70e261 failed to exit within 2 seconds of SIGTERM - using the force" May 29 22:13:57 master docker[943]: time="2016-05-29T22:13:57.713825681Z" level=info msg="Container 0062afb8c56d78758e068985e59f7f69b1bc9b880573d20e9f51083ccab9487a failed to exit within 2 seconds of SIGTERM - using the force" May 29 22:13:57 master docker[943]: time="2016-05-29T22:13:57.718193803Z" level=info msg="Container a120c3e472f8145db61c0f1f9d21301822781a2dcd914e02d2080335e8935c20 failed to exit within 2 seconds of SIGTERM - using the force" May 29 22:13:57 master systemd-journald[64414]: Journal stopped May 29 22:13:57 master systemd-journald[2398]: Runtime journal (/run/log/journal/) is 34.4M, max 34.3M, 0B free. May 29 22:13:57 master systemd-journald[64414]: Received SIGTERM from PID 943 (docker). May 29 22:13:57 master systemd[1]: Started Login Service. May 29 22:13:57 master systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart. May 29 22:13:57 master systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart. May 29 22:13:57 master systemd[1]: getty@tty1.service: Service has no hold-off time, scheduling restart. May 29 22:13:57 master systemd[1]: systemd-udevd.service: Service has no hold-off time, scheduling restart. May 29 22:13:57 master systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart. May 29 22:13:57 master kernel: cbr0: port 10(veth625bdc9) entered disabled state May 29 22:13:57 master kernel: cbr0: port 9(vethda8ad51) entered disabled state May 29 22:13:57 master kernel: device vethda8ad51 left promiscuous mode May 29 22:13:57 master kernel: cbr0: port 9(vethda8ad51) entered disabled state May 29 22:13:57 master kernel: cbr0: port 11(veth1335787) entered disabled state May 29 22:13:57 master kernel: cbr0: port 8(veth842eb8f) entered disabled state May 29 22:13:57 master kernel: cbr0: port 4(veth1386aab) entered disabled state May 29 22:13:57 master kernel: cbr0: port 7(vethc9a4089) entered disabled state May 29 22:13:57 master kernel: device veth1335787 left promiscuous mode May 29 22:13:57 master kernel: cbr0: port 11(veth1335787) entered disabled state May 29 22:13:57 master kernel: device veth842eb8f left promiscuous mode May 29 22:13:57 master kernel: cbr0: port 8(veth842eb8f) entered disabled state May 29 22:13:57 master kernel: device veth1386aab left promiscuous mode May 29 22:13:57 master kernel: cbr0: port 4(veth1386aab) entered disabled state May 29 22:13:57 master kernel: device vethc9a4089 left promiscuous mode May 29 22:13:57 master kernel: cbr0: port 7(vethc9a4089) entered disabled state May 29 22:13:57 master systemd[1]: unscd.service: Service hold-off time over, scheduling restart. May 29 22:13:57 master systemd[1]: walinuxagent.service: Service hold-off time over, scheduling restart. May 29 22:13:57 master systemd[1]: Stopped Azure Linux Agent. May 29 22:13:57 master systemd[1]: Started Azure Linux Agent. May 29 22:13:57 master systemd[1]: Stopped Name Service Cache Daemon. May 29 22:13:57 master systemd[1]: Started Name Service Cache Daemon. May 29 22:13:57 master systemd[1]: Stopped Flush Journal to Persistent Storage. May 29 22:13:57 master systemd[1]: Stopping Flush Journal to Persistent Storage... May 29 22:13:57 master systemd[1]: Stopped Journal Service. May 29 22:13:57 master systemd[1]: Starting Journal Service... May 29 22:13:57 master systemd[1]: Stopped udev Kernel Device Manager. May 29 22:13:57 master systemd[1]: Starting udev Kernel Device Manager... May 29 22:13:57 master systemd[1]: Stopped Getty on tty1. May 29 22:13:57 master systemd[1]: Started Getty on tty1. May 29 22:13:57 master systemd[1]: Stopped Login Service. May 29 22:13:57 master systemd[1]: Starting Login Service... May 29 22:13:57 master systemd[1]: Stopped Network Time Synchronization. May 29 22:13:57 master systemd[1]: Starting Network Time Synchronization... May 29 22:13:57 master systemd[1]: Starting OpenBSD Secure Shell server... May 29 22:13:57 master systemd[1]: serial-getty@ttyS0.service: Service hold-off time over, scheduling restart. May 29 22:13:57 master systemd-journald[2398]: Journal started ``` These things jumped out as being suspicious: * `May 29 22:13:56 master kernel: eth0: renamed from vethd82d06e` * `May 29 22:13:56 master docker[943]: time="2016-05-29T22:13:56.448536888Z" level=warning msg="Error getting v2 registry: Get https://registry-1.docker.io/v2/: dial tcp 52.203.89.113:443: connect: network is unreachable"` ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586856 Title: docker sends sigterm to systemd-journald and soft reboots the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1586856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
