mirror of
https://github.com/kata-containers/kata-containers.git
synced 2026-02-21 22:34:29 +00:00
20ca4d2d79
1. Add disable_block_device_use to CLH settings file, for parity with the already existing QEMU settings. 2. Set DEFDISABLEBLOCK := true by default for both QEMU and CLH. After this change, Kata Guests will use by default virtio-fs to access container rootfs directories from their Hosts. Hosts that were designed to use Host block devices attached to the Guests can re-enable these rootfs block devices by changing the value of disable_block_device_use back to false in their settings files. 3. Add test using container image without any rootfs layers. Depending on the container runtime and image snapshotter being used, the empty container rootfs image might get stored on a host block device that cannot be safely hotplugged to a guest VM, because the host is using the same block device. 4. Add block device hotplug safety warning into the Kata Shim configuration files. Signed-off-by: Dan Mihai <dmihai@microsoft.com> Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com> Signed-off-by: Cameron McDermott <cameron@northflank.com>
Design
Kata Containers design documents:
- Kata Containers architecture
- API Design of Kata Containers
- Design requirements for Kata Containers
- VSocks
- VCPU handling(in runtime-go)
- VCPU handling(in runtime-rs)
- VCPU threads pinning
- Host cgroups
- Agent systemd cgroup
InotifysupportHookssupport- Metrics(Kata 2.0)
- Metrics in Rust Runtime(runtime-rs)
- Design for Kata Containers
Lazyloadability withnydus - Design for direct-assigned volume
- Design for core-scheduling
- Virtualization Reference Architecture