
Update Kata containers docs Fix conflict Story: 2010765 Task: 49554 Change-Id: I07e31de31baca504e073efc5358ab664d9355909 Signed-off-by: Elisamara Aoki Goncalves <elisamaraaoki.goncalves@windriver.com>
1.6 KiB
Known Kata Container Limitations
This section describes the known limitations when using Kata containers.
SR-IOV Support
A minimal kernel and rootfs for
Kata containers are shipped with , and can be found at
/usr/share/kata-containers/
. To enable certain kernel
features such as IOMMU (I/O memory management unit)
, and desired
network kernel modules, a custom kernel image, and rootfs has to be
built. However, many tests carried out using this solution were
unsuccessful. More details of this solution can be seen in: https://bugs.launchpad.net/starlingx/+bug/1867927.
CPU Manager Support
Kata containers currently occupy only the platform cores. There is no
CPU (Central Processing Unit)
manager support.
Hugepages
- Similar to the limitation, hugepage support must be configured in a custom Kata kernel.
- The size and number of hugepages must be written using the
io.katacontainers.config.hypervisor.kernel_params
annotation. - Creating a
hugetlbfs
mount for hugepages in the Kata container is specific to the end user application.
Note
This solution does not work in version v3.1.3 of the Kata Containers. A pod can be started with hugepages specified, but none are actually allocated to the Kata .