according to the logs it might affect more docker than the kernel:
- docker is used on that system (at least since Aug 1st)
- but I cannot find that docker.io is used - which docker version is in use?
dpkg log doesn't show me that docker.io got installed
- seems to be a docker issue that is causing a crash
occurs multiple times per second
Aug 2 06:26:51 zml025 dockerd[6150]:
time="2017-08-02T06:26:51.327342000-04:00" level=error msg="Handler for GET /
containers/18ffa76eaba65e5f451a3d56821d3f90a58dac74021ea7a5114352a2d6816d0d/json
returned error: No such container:
18ffa76eaba65e5f451a3d56821d3f90a58dac74021ea7a5114352a2d6816d0d"
- the kernel log also shows some issues:
the following is a known docker issue, seems to be caused by privileged
containers:
https://github.com/moby/moby/issues/21081
https://github.com/kubernetes/kubernetes/issues/27885
Aug 1 03:17:19 zml025 kernel: [15074.536567] aufs
au_opts_verify:1597:dockerd[6723]:
dirperm1 breaks the protection by the permission bits on the lower
branch
- kernel log:
another issue also known by docker:
https://github.com/moby/moby/issues/14807
Aug 1 03:17:19 zml025 kernel: [15074.649870] device vetha553aad
entered promiscuous mode
Aug 1 03:17:19 zml025 kernel: [15074.649937] IPv6:
ADDRCONF(NETDEV_UP): vetha553aad: link is not ready
Aug 1 03:17:19 zml025 kernel: [15074.649939] docker0: port
1(vetha553aad) entered forwarding state
Aug 1 03:17:19 zml025 kernel: [15074.649943] docker0: port
1(vetha553aad) entered forwarding state
Aug 1 03:17:19 zml025 kernel: [15074.650259] docker0: port
1(vetha553aad) entered disabled state
Aug 1 03:17:19 zml025 kernel: [15075.283565] eth0: renamed from
vethd76add0
Aug 1 03:17:20 zml025 kernel: [15075.334494] IPv6:
ADDRCONF(NETDEV_CHANGE): vetha553aad: link becomes ready
Aug 1 03:17:20 zml025 kernel: [15075.334520] docker0: port
1(vetha553aad) entered forwarding state
Aug 1 03:17:20 zml025 kernel: [15075.334527] docker0: port
1(vetha553aad) entered forwarding state
Aug 1 03:17:20 zml025 kernel: [15075.334549] IPv6:
ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
- duplicate IPv6 addresses needs to be fixed
Aug 1 03:17:20 zml025 kernel: [15075.611749] IPv6: eth0: IPv6 duplicate
address fe80::42:acff:fe11:2 detected!
** Bug watch added: github.com/moby/moby/issues #21081
https://github.com/moby/moby/issues/21081
** Bug watch added: github.com/kubernetes/kubernetes/issues #27885
https://github.com/kubernetes/kubernetes/issues/27885
** Bug watch added: github.com/moby/moby/issues #14807
https://github.com/moby/moby/issues/14807
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708399
Title:
kernel panic -not syncing: Fatal exception: panic_on_oops
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708399/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
