firecracker-containerd
firecracker-containerd copied to clipboard
firecracker-containerd enables containerd to manage containers as Firecracker microVMs
Although arm64 architecture was not formally claimed supported, it may be worthy to try and to see what's happening there. I tried to follow the get-started page (https://github.com/firecracker-microvm/firecracker-containerd/blob/master/docs/getting-started.md) on an...
While Firecracker is [recommending customers to use a jailer in production](https://github.com/firecracker-microvm/firecracker/blob/master/docs/prod-host-setup.md); > Using Jailer in a production Firecracker deployment is highly recommended, as it provides additional security boundaries for the...
Hello everyone. I learn how to use firecracker. I wrote [article about installing firecracker on CentOS 7, russian language](https://www.hdfilm.kz/blog/2020/05/18/run-firecracker-at-centos7-machines/). Now i want to use docker that run containers in firecracker....
take a container stdout example 1. agent receive container stdout from fifo in vm 2. agent listen unix and send stdout to runtime with vsock 3. runtime receive stdout and...
Firecracker is going to have micro VM snapshotting and we'd like to utilize that on firecracker-containerd. First we are going to update the SDK (see https://github.com/firecracker-microvm/firecracker-go-sdk/issues/239).
While we want to make firecracker-containerd mostly containerd-compatible, there were incompatibilities like #457. Finding and fixing incompatibilities is one. Building a mechanism to prevent incompatibilities is another one, which could...
I would like to know if you guys already placed a solution or run multiple services inside the micro VM that uses the same port, I'm researching how to run...
I would like to suppress all logging below "warning" or "fatal" but firecracker-containerd does not account for the options provided in config.toml or in CLI. Example: ``` sudo firecracker-containerd --config...
@nmeyerhans brought up during a review that we currently we only do fairly limited validation of various paths provided to firecracker-containerd. For example, [the paths provided for the container rootfs](https://github.com/firecracker-microvm/firecracker-containerd/blob/38742eeb4fb5d549b31727a57b8c79e88b204b59/runtime/service.go#L775-L776)...
Currently, clients using the fc-control client are able to receive [grpc error codes](https://godoc.org/google.golang.org/grpc/codes) in error objects returned by API calls, but those are very generic error types that don't communicate...