Skip to content

e2e: containerd requires kernel CONFIG_FS_VERITY=y - #798

Merged
klihub merged 1 commit into
containers:mainfrom
askervin:5jD-e2e-fix-k8s-with-custom-kernels
Sep 17, 2026
Merged

klihub merged 1 commit into
containers:mainfrom
askervin:5jD-e2e-fix-k8s-with-custom-kernels

Conversation

@askervin

Copy link
Copy Markdown
Collaborator

This change updates custom kernel configs to support latest containerd. Containerd enables fs-verity on every blob it writes into its content store when the filesystem supports it. Without FS_VERITY every open() of such a blob fails with EOPNOTSUPP, so no image can be unpacked and kubernetes never starts.

This change updates custom kernel configs to support latest
containerd. Containerd enables fs-verity on every blob it writes into
its content store when the filesystem supports it. Without FS_VERITY
every open() of such a blob fails with EOPNOTSUPP, so no image can be
unpacked and kubernetes never starts.

Signed-off-by: Antti Kervinen <antti.kervinen@intel.com>
@klihub
klihub merged commit 27d4851 into containers:main Sep 17, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants