Hi Dan, We run a bunch of instances both on AWS and GCP, and we run a significant number of containers on both. We've only ever seen this problem on GCP and never on AWS (it's baffling!). The kernels are as- close-as-possible and the rest (Ubuntu version / Docker version / etc) are identical. To answer your questions:
-what release are you using (trusty/xenial/zesty)? Xenial -what kernel version are you using? 4.13.0-1008-gcp -do you have specific steps to reproduce the problem? Unfortunately we don't. It just happens on its own after 1/2 weeks. The following shows in dmesg: [1015401.681728] unregister_netdevice: waiting for veth251ecfe to become free. Usage count = 1 [1015411.761772] unregister_netdevice: waiting for veth251ecfe to become free. Usage count = 1 [1015421.841740] unregister_netdevice: waiting for veth251ecfe to become free. Usage count = 1 [1015431.953729] unregister_netdevice: waiting for veth251ecfe to become free. Usage count = 1 etc etc We've tried a few things including upgrading kernel and disabling IPv6 to no avail. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711407 Title: unregister_netdevice: waiting for lo to become free Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: This is a "continuation" of bug 1403152, as that bug has been marked "fix released" and recent reports of failure may (or may not) be a new bug. Any further reports of the problem should please be reported here instead of that bug. -- [Impact] When shutting down and starting containers the container network namespace may experience a dst reference counting leak which results in this message repeated in the logs: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] See comment 16, reproducer provided at https://github.com/fho/docker- samba-loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
