Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Documentation: Firecracker limitations #351

Closed
5 tasks
egernst opened this issue Jan 23, 2019 · 4 comments
Closed
5 tasks

Documentation: Firecracker limitations #351

egernst opened this issue Jan 23, 2019 · 4 comments
Labels
limitation Issue cannot be resolved

Comments

@egernst
Copy link
Member

egernst commented Jan 23, 2019

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

@mcastelino
Copy link

@mcastelino
Copy link

@mcastelino
Copy link

@mcastelino mcastelino changed the title documentation: firecracker limitations Documentation: Firecracker limitations Jan 23, 2019
@mcastelino mcastelino added the limitation Issue cannot be resolved label Jan 23, 2019
@grahamwhaley
Copy link
Contributor

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?
I've added a couple to the wiki page as a start:

  • must have vhost_vsock
  • must have block based storage backend

Please add more here, and to the wiki page, if you know of them.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
limitation Issue cannot be resolved
Projects
None yet
Development

No branches or pull requests

4 participants