Hello and thanks for this bug report. I had a look a the runc bug reports and changes to see if I could easily spot a relevant change, but I couldn't. I don't have a good hypothesis of what could be wrong, but I'd start checking if the newer runc is causing a higher memory or CPU usage, causing components to timeout ("context deadline exceeded") or OOMs.
Could you please: - Attach the kernel log (dmesg) to this bug, captured after hitting those containerd errors? - Check the system load and memory usage when using the two different versions of runc. This could be done for example via something like `vmstat -S M 5`. If no useful clues are found, then I think we'll have to bisect. ** Changed in: runc (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927219 Title: context deadline exceeded: unknown in containerd with latest runc version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1927219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs