Files
kata-containers/docs/how-to
Aurélien Bombo 6ff78373cf docs: Document privileged_without_host_devices=false as unsupported
Document that privileged containers with
privileged_without_host_devices=false are not generally supported.

When you try the above, the runtime will pass all the host devices to Kata
in the OCI spec, and Kata will fail to create the container for various
reasons depending on the setup, e.g.:

 - Attempting to hotplug uninitialized loop devices.
 - Attempting to remount /dev devices on themselves when the agent had
   already created them as default devices (e.g. /dev/full).
 - "Conflicting device updates" errors.
 - And more...

privileged_without_host_devices was originally created to support
Kata [1][2] and lots of people are having issues when it's set to
false [3].

[1] https://github.com/kata-containers/runtime/issues/1568
[2] https://github.com/containerd/cri/pull/1225
[3] https://github.com/kata-containers/kata-containers/issues?q=is%3Aissue%20%20in%3Atitle%20privileged

Signed-off-by: Aurélien Bombo <abombo@microsoft.com>
2025-10-02 15:21:19 -05:00
..
2024-09-19 16:05:43 +02:00

Howto Guides

Kubernetes Integration

Hypervisors Integration

Currently supported hypervisors with Kata Containers include:

  • qemu

  • cloud-hypervisor

  • firecracker

    In the case of firecracker the use of a block device snapshotter is needed for the VM rootfs. Refer to the following guide for additional configuration steps:

Confidential Containers Policy

Advanced Topics