This repository has been archived by the owner on May 12, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 302
Documentation: Firecracker limitations #351
Labels
limitation
Issue cannot be resolved
Comments
Just a note - when we do finally write the kata/fc docs into a markdown, can we also list the pre-requisites along with the limitations?
Please add more here, and to the wiki page, if you know of them. |
This was referenced Aug 26, 2019
This was referenced Nov 18, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With its limited feature support, there are expected functional limitations when using Kata Containers with the Firecracker hypervisor.
This issue serves as a location to track these limitations.
Volume Support and Host to Guest file sharing Firecracker Limitation: volume support runtime#1071
Due to lack of host to guest file sharing support in Firecracker, volumes and more importantly Kubernetes secrets and config maps do not work. This means that some Kubernetes features do not current work with Firecracker.
Resizing of CPU and Memory resource constraints
Kata containers does not support resizing of Firecracker PODs.
Additionally as the support for Firecracker is preliminary, some features are yet to be implemented in the runtime. These include
Kata containers today does not support choosing between multiple hypervisors using a single configuration.toml. There is a workaround possible today using a wrapper shell script to provide an alternate configuration file, which allows kata-runtime to support multiple hypervisors on the same node as shown here
https://github.com/clearlinux/cloud-native-setup/blob/master/clr-k8s-examples/setup_kata_firecracker.sh#L63
Kata containers does not use jailer to constrain firecracker.
Kata containers does not apply the container CPU and Memory constraints for Firecracker PODs.
The text was updated successfully, but these errors were encountered: