[Risc-V] CPU at 100% on container deletion with crun+Docker #3389
Description
Recently Containerd PR #3328 was upstreamed adding support for the Risc-V architecture.
The daemon is using crun CRI (https://github.com/giuseppe/crun) as the runtime due to runc dependency on CGO which is still not available on the arch.
I saw a behavior where after deleting a container, containerd spins up the CPU to 100% and stays until restarted.
Here is a demonstration of the error:
To reproduce, I have packed a Risc-V Qemu VM and the Docker, Crun and Containerd binaries tarball. There is a install script in the tarball and more details in the tracker repo.
Software Versions:
carlosedp in ~ at fedora-unleashed
➜ crun --version
crun 0.6
carlosedp in ~ at fedora-unleashed
➜ containerd --version
containerd github.com/containerd/containerd 1.2.0+unknown
carlosedp in ~ at fedora-unleashed
➜ docker version
Client:
Version: unknown-version
API version: 1.40
Go version: devel +2bdba6c078 Fri May 24 18:40:32 2019 +0000
Git commit: unknown-commit
Built: unknown-buildtime
OS/Arch: linux/riscv64
Experimental: true
Server:
Engine:
Version: library-import
API version: 1.41 (minimum version 1.12)
Go version: devel +2bdba6c078 Fri May 24 18:40:32 2019 +0000
Git commit: library-import
Built: library-import
OS/Arch: linux/riscv64
Experimental: false
containerd:
Version: 1.2.0+unknown
GitCommit:
docker-init:
Version: 0.18.0
GitCommit: 3c53686
Any pointers on how to debug this?
Cc. @tonistiigi