** Description changed: Following LP #2063442 which added docker to the needrestart exclusion list, containerd should also be excluded. - **Problem:** + Problem: When needrestart restarts services after a libc6 upgrade, it restarts containerd but NOT docker (because docker is excluded). This causes docker to lose its RPC connection to containerd, breaking container networking. - **Timeline from affected system (Ubuntu 24.04):** + Timeline from affected system (Ubuntu 24.04): - 05:07:00 - libc6 upgraded via unattended-upgrades - 05:07:13 - needrestart restarts containerd (not excluded) - 05:07:13 - docker loses RPC connection: "Failed to get event: rpc error: code = Unavailable desc = error reading from server: EOF" - Result: Docker containers lose network connectivity until manual reboot - **Expected behavior:** + Expected behavior: Since docker depends on containerd, both should be excluded from automatic restarts. - **Suggested fix:** + Suggested fix: Add to /etc/needrestart/needrestart.conf: - qr(^containerd) => 0, + qr(^containerd) => 0, - **System information:** + System information: - Ubuntu 24.04 LTS - needrestart 3.6-7ubuntu4.5 - Docker installed from official Docker repository - **Workaround:** + Workaround: Manually add `qr(^containerd) => 0,` to /etc/needrestart/needrestart.conf
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2139422 Title: needrestart should also exclude containerd alongside docker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2139422/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
