Increased CPU usage after Docker upgrade (runc init)

General
,
1

Recently, I’ve upgraded Docker from 18 to 20.10.13 and I noticed increased CPU usage caused probably by runc init process that appears every few seconds in processes with ~15-20% CPU usage. I’m running same docker version on much smaller server and CPU usage there as much lower.

Client:
 Version:           20.10.13
 API version:       1.41
 Go version:        go1.20.10
 Git commit:        a224086
 Built:             Wed Oct 25 23:10:16 2023
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server:
 Engine:
  Version:          20.10.13
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.20.10
  Git commit:       906f57f
  Built:            Wed Oct 25 23:12:38 2023
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.13
  GitCommit:        9cc61520f4cd876b86e77edfeb88fbcd536d1f9d
 runc:
  Version:          1.0.3
  GitCommit:        f46b6ba2c9314cfc8caae24a32ec5fe9ef1059fe
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

SCR-20231210-siml
SCR-20231210-siml1745×702 45.9 KB

Any ideas how to find a cause? The presented CPU usage is during with ~6 idle containers. I’ve tried to reboot the server, but it didn’t help.

Edit: Okay, I reverted docker to previous version, together with containerd, and runc. It works fine now. I think I will keep it as it is.