mirror of
https://github.com/kata-containers/kata-containers.git
synced 2026-07-26 07:30:19 +00:00
2d56b83411
EROFS fs-verity depends on the backing filesystem supporting fs-verity, which cannot be guaranteed on an arbitrary node. Rather than gate the NVIDIA CPU profile on a host feature we do not control, disable fs-verity so it works on the widest possible range of setups; we take that hit deliberately to keep the profile generic. Move this out of the test harness and into the kata-deploy NVIDIA CPU profile: try-kata-nvidia-cpu.values.yaml now ships a containerd erofs snapshotter drop-in that disables fs-verity and pins the memory-backed default_size, and selects memory-backed rw layers with dm-verity for the lower (image) layers. Because containerd.userDropIn is loaded after kata-deploy's generated config, it overrides the built-in enable_fsverity default. The CI helm helper no longer special-cases NVIDIA CPU to inject enable_fsverity=false. Instead it honors an erofs snapshotter drop-in already provided by the base values file and only synthesizes the default default_size drop-in when the profile does not provide its own. Note that this drop-in targets containerd's built-in EROFS snapshotter, available only on containerd >= 2.2.0 (config version 3, conf.d auto-import), which is the same minimum kata-deploy already enforces for the EROFS snapshotter. Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com> Assisted-by: Cursor with Claude Opus 4.8
Kata Containers Tests
This directory contains various types of tests for testing the Kata Containers repository.
Test Content
We provide several tests to ensure Kata-Containers run on different scenarios and with different container managers.
- Integration tests to ensure compatibility with:
- Stability tests
- Functional
GitHub Actions
Kata Containers uses GitHub Actions in the Kata Containers repository.