Fabiano Fidêncio 72fb41d33b kata-deploy: Symlink original config to per-shim runtime copy ...

Users were confused about which configuration file to edit because
kata-deploy copied the base config into a per-shim runtime directory
(runtimes/<shim>/) for config.d support, leaving the original file
in place untouched.  This made it look like the original was the
authoritative config, when in reality the runtime was loading the
copy from the per-shim directory.

Replace the original config file with a symlink pointing to the
per-shim runtime copy after the copy is made.  The runtime's
ResolvePath / EvalSymlinks follows the symlink and lands in the
per-shim directory, where it naturally finds config.d/ with all
drop-in fragments.  This makes it immediately obvious that the
real configuration lives in the per-shim directory and removes the
ambiguity about which file to inspect or modify.

During cleanup, the symlink at the original location is explicitly
removed before the runtime directory is deleted.

Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com>

2026-04-09 17:16:40 +02:00

..

osbuilder

rootfs: add runtime support for NVAT

2026-04-06 17:51:12 +00:00

packaging

kata-deploy: Symlink original config to per-shim runtime copy

2026-04-09 17:16:40 +02:00

testing

tests: Set sev-snp, qemu-snp CIs as required

2026-04-08 22:36:58 +02:00

containerd-shim-katadbg-v2

tests: Make editorconfig-checker happy

2026-02-10 21:58:28 +01:00