Closed 915604903T closed 4 years ago
did you enable devicemapper?
Given that we are missing information on this bug we are closing this for now. Feel free to reopen this bug once information is added. We would also appreciate getting relevant logs.
Description of problem
I followed this documentation. I want to run kata-firecracker via containerd. I created /usr/local/bin/containerd-shim-katafc-v2:
And the content of configuration-fc.toml above is as following:
The kata-runtime version is 1.10.0. The firecracker version is 0.21.0. The containerd version is 1.3.2. Then I executed command
sudo ctr run --runtime io.containerd.run.katafc.v2 -t --rm docker.io/library/busybox:latest hello sh
.Expected result
I expected the container boot up normally with a interactive shell.
Actual result
I can use docker to boot up a container whose runtime is kata-fc successfully and execute
sudo ctr run --runtime io.containerd.run.kata.v2 -t --rm docker.io/library/busybox:latest hello sh
successfully. But when I wanted to use ctr to start a kata-firecracker runtime container, It returned the error message at the first time:ctr: ttrpc: closed: unknown
And at the second time, it just hung up.