Closed bchalios closed 4 years ago
My EC2 Debian box is 4.9.0, and firecracker-containerd is working fine. The exact version seems slightly newer than what you have though.
% uname -a
Linux ip-172-31-27-222 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3 (2019-09-02) x86_64 GNU/Linux
Can you upgrade the Linux kernel on the x86 host?
Also what is the kernel version the Raspberry Pi host is using? Did you get the exact same error?
Hi there,
I upgraded the kernel:
$ uname -r
5.5.0-rc3
and I still get the same error. It could very well be that I 'm doing something wrong with my setup, but I can't figure out what.
Sorry, the rpi4 runs on this:
uname -r
4.19.75-v8+
ok, fixed, it myself.
The problem was not with the environment. The problem was with the rootfs.img
. I had a problem with my docker setup, so I could not run make image
from the topdir. Instead I had run make rootfs.img
from inside tools/image-builder
. That image was not working properly, for some reason. Does that make sense?
Hmm, what was the error you got from make image
? We'd like to fix the issue if we can.
Resolving. Please feel free to ping us regarding the make image
issue!
I am experiencing an error when trying to follow the Getting Started steps from here.
The symptoms of the problem are the following:
I start
firecracker-containerd
like this:then on a different terminal I try to launch a container:
And here are the logs of
firecracker-containerd
when I try to launch the container:My machine has the following specs:
I have spoken with @nmeyerhans which pointed out, that my kernel is not officially supported by firecracker, and that could be a potential problem. In the meantime, I reproduced the problem on a raspberry pi 4. I managed to build
firecracker containerd
as is on the board andfirecracker 0.20.1
(which is needed in order to run on RPi4)