I was experiencing a situation with moby dockerd entering a state similar to comment 0 here, running kubernetes and linux kernel 4.15.0-1037-azure. This was an 8 node cluster. Observed with combinations:
kubernetes 1.11.5 + moby runtime 3.0.1 + Ubuntu 16.04.5 kubernetes 1.11.7 + moby runtime 3.0.4 + Ubuntu 16.04.10 The longest window between outages prior was 4 days, with the shortest being less than a day. I have observed 2 weeks of uptime on 8 nodes without observation of the original symptoms since upgrading the kubernetes node kernel to 4.15.0-1040-azure. I am confident the kernel patch has resolved our problem. Ref https://github.com/moby/moby/issues/38750 and https://github.com/Azure/AKS/issues/838, both closed. ** Bug watch added: github.com/moby/moby/issues #38750 https://github.com/moby/moby/issues/38750 ** Bug watch added: github.com/Azure/AKS/issues #838 https://github.com/Azure/AKS/issues/838 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
