Commit Graph
7 Commits
Author SHA1 Message Date
Chris Henzie 93f7a62e50 Support both styles of volatile mount option
Kernel 6.12.80+ returns 'fsync=volatile' instead of just 'volatile'
in mount options, which breaks containerd's exact string matching
checks.

Fixes this issue by adding support for 'fsync=volatile' in addition
to the existing 'volatile' check in RemoveVolatileOption and
addVolatileOptionOnImageVolumeMount.

Assisted-by: Antigravity
Signed-off-by: Chris Henzie <chrishenzie@gmail.com>
2026-04-20 11:50:57 -07:00
qiuxue db9546b6df cri: Fix image volumes with user namespaces
Signed-off-by: qiuxue <liuyutao36@gmail.com>
2026-02-06 23:41:17 +08:00
Jin Dong cff8184ffb support image volume sub path
Signed-off-by: Jin Dong <djdongjin95@gmail.com>
2025-06-03 21:53:29 -04:00
Wei Fu fe4703cde5 integration: check image volume snapshot after deleting pod
Signed-off-by: Wei Fu <fuweid89@gmail.com>
2025-03-25 15:52:15 -04:00
Wei Fu d141d6c3dd integration: run image volumes for linux platform only
Signed-off-by: Wei Fu <fuweid89@gmail.com>
2025-03-25 15:23:47 -04:00
Wei Fu de833ebbbe cri: enhance error handling for image volume
Signed-off-by: Wei Fu <fuweid89@gmail.com>
2025-03-25 15:16:59 -04:00
Wei Fu be0ab6e936 cri: add volatile option to image volume mount if applicable
Unmounting a writable overlayfs can trigger [syncfs][1], causing I/O pressure
and impacting running containers. If possible, we should apply volatile
option to image volume mount.

REF:

[1]: https://github.com/containerd/containerd/pull/6478

Signed-off-by: Wei Fu <fuweid89@gmail.com>
2025-03-25 15:16:40 -04:00