You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(box): CRI writable volume mounts via copy materialization
CreateContainer previously rejected any writable mount and any
selinux_relabel mount with Unimplemented, so the "starting container with
volume" conformance specs (which mount a host dir writable with
SelinuxRelabel=true) failed. Both are now accepted:
- Writable mounts are materialized like read-only ones — the source is
COPIED into the container rootfs at container_path. The host-created
content is visible in the container and the container may write to its
copy. NOTE: writes do NOT propagate back to the host source (microVM
containers cannot bind-mount host paths post-boot); sufficient for
read-oriented volumes + the conformance, logged as a warning.
- selinux_relabel is a no-op on this non-SELinux runtime; accepted rather
than failing the container.
Non-private mount propagation (rshared/rslave/rprivate) remains
Unimplemented — it needs a real shared mount, not a copy.
Verified on the KVM server: "starting container with volume [Conformance]"
and "...when host path is a symlink" both pass; build + clippy clean, 219
cri tests pass (rejection test replaced with a writable-materialize test).
0 commit comments