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
SingularityCE 4.0 introduced the OCI-SIF format, where OCI images are embedded in a SIF, using OCI structures... albeit with a single SquashFS layer for the rootfs.
SingularityCE 4.1 allowed layers to be preserved, but converted to SquashFS, when an OCI image is pulled to an OCI-SIF.
We want to allow an OCI-SIF to be pushed to a registry, such that the image in the registry is in 'true' OCI format, with tar layers.
This would allow lossless round-tripping between SingularityCE's OCI-Mode / OCI-SIF and other OCI runtimes through an OCI registry.
On push with a non-default flag, the image should be converted back into tar layer format before or during the push process.
The text was updated successfully, but these errors were encountered:
SingularityCE 4.0 introduced the OCI-SIF format, where OCI images are embedded in a SIF, using OCI structures... albeit with a single SquashFS layer for the rootfs.
SingularityCE 4.1 allowed layers to be preserved, but converted to SquashFS, when an OCI image is pulled to an OCI-SIF.
We want to allow an OCI-SIF to be pushed to a registry, such that the image in the registry is in 'true' OCI format, with tar layers.
This would allow lossless round-tripping between SingularityCE's OCI-Mode / OCI-SIF and other OCI runtimes through an OCI registry.
On push with a non-default flag, the image should be converted back into tar layer format before or during the push process.
The text was updated successfully, but these errors were encountered: