Hi, Here is the kern.log extract of the time containers were trying to start. I only see logs about network interfaces, and the log is full of it. I don't see those logs anymore after the runc version downgrade.
It looks like just a consequence of the runner's start failure. About the load, I don't think it was very high, the server is quite powerful (256GB of RAM, 16 core / 32 threads). I experienced the problem on a production system during what should have been a quick server reinstall during late maintenance hours, so I might be mistaken about the load at that time. I'll try to reproduce the issue on a test environment this weekend to get real load figures with both versions of runc & allow further testing. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1927219/+attachment/5495606/+files/kern_extract.log -- 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
