Fabiano Fidêncio e9622481f0 cri: propagate runtime-specific snapshotters to image service ...

When users configure a snapshotter in the runtime config (e.g.,
`plugins."io.containerd.cri.v1.runtime".containerd.runtimes.kata.snapshotter`),
the CRI image service was not aware of this configuration. This caused
images to be pulled with the default snapshotter instead of the
runtime-specific one, because the image service's runtimePlatforms map
was not populated with these runtime-to-snapshotter mappings.

Let's make sure that during the CRI plugin init, we iterate over all the
configured runtimes, and propagate any snapshotter configuration to the
image service.

The issue was found while working on #12835.

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

2026-02-20 23:05:46 +01:00

..

images

Default config_path if legacy registry options are not set.

2025-10-16 17:51:44 -07:00

runtime

Fix directory permissions

2025-11-04 16:04:30 +09:00

cri_test.go

complete cri grpc config migration

2024-11-27 21:06:00 +00:00

cri.go

cri: propagate runtime-specific snapshotters to image service

2026-02-20 23:05:46 +01:00