fix: use .part extension (Talos CRI reads .part not .toml)

Author: shtse8

20-devmapper.toml 20-devmapper.part20-devmapper.toml renamed to 20-devmapper.part

@@ -15,7 +15,7 @@ COPY devmapper-pool.yaml /rootfs/usr/local/etc/containers/devmapper-pool.yaml
 # BEFORE CRI initializes devmapper plugin (~2-3s), devmapper loads on first boot.
 # If CRI starts first: devmapper plugin fails gracefully (disabled), runc works.
 # Extension also writes config to overlay dir as fallback for next CRI restart.
-COPY 20-devmapper.toml /rootfs/usr/local/etc/cri/conf.d/20-devmapper.toml
+COPY 20-devmapper.part /rootfs/usr/local/etc/cri/conf.d/20-devmapper.part
 
 # Extension service: creates thin pool at boot
 COPY --from=tools /bin/busybox.static /rootfs/usr/local/lib/containers/devmapper-pool/bin/busybox

Dockerfile

@@ -15,7 +15,7 @@ META_FILE="${META_DIR}/meta"
 # Writing to the overlay upper dir makes files appear in /etc/cri/conf.d/
 # when CRI reads it. This is under /var (mounted into this container).
 CRI_CONF_DIR="/var/system/overlays/etc-cri-diff/conf.d"
-CRI_CONF="${CRI_CONF_DIR}/20-devmapper.toml"
+CRI_CONF="${CRI_CONF_DIR}/20-devmapper.part"
 HOST_PROC="/host-proc"
 # Marker file to prevent reboot loop — written after first successful reboot-triggering run
 REBOOT_MARKER="/var/lib/devmapper/.rebooted"