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
At present, the --oci mode relies on unprivileged overlay support in the kernel. This is not available on all systems. Introduced in mainline kernel 5.13. it has been backported to some distributions using older kernels, but not others.
We have some code that can check for unprivileged kernel overlay support here:
This check is currently used in native mode. Where unpriv kernel overlay is not supported, native mode will switch to an 'underlay' approach... in which many (many many) bind mounts are used, instead of an overlayfs mount, to assemble the combined view of the rootfs and --overlay source.
Underlay is complex and tied to the native runtime session layout. I don't think we want to implement it for --oci mode unless we fins a compelling reason to do so.
At present, the
--oci
mode relies on unprivileged overlay support in the kernel. This is not available on all systems. Introduced in mainline kernel 5.13. it has been backported to some distributions using older kernels, but not others.We have some code that can check for unprivileged kernel overlay support here:
https://github.com/sylabs/singularity/blob/main/internal/pkg/util/fs/overlay/overlay_linux.go#L141
This check is currently used in native mode. Where unpriv kernel overlay is not supported, native mode will switch to an 'underlay' approach... in which many (many many) bind mounts are used, instead of an overlayfs mount, to assemble the combined view of the rootfs and
--overlay
source.Underlay is complex and tied to the native runtime session layout. I don't think we want to implement it for
--oci
mode unless we fins a compelling reason to do so.Instead, the OverlaySet code should use
fuse-overlayfs
(https://github.com/containers/fuse-overlayfs) if kernel unprivileged overlays are not available.Implement an automatic check, prioritising kernel unprivileged overlay, but falling back to
fuse-overlayfs
.The text was updated successfully, but these errors were encountered: