[FEATURE] CRI-O runtime support

[prafgup]

Description

Hi maintainers,

I'd like to request support for CRI-O runtime, particularly for running SOCI on OpenShift clusters.
Currently, SOCI only supports containerd as the runtime. However, OpenShift (and other Kubernetes distributions) use CRI-O as their default container runtime. This limits SOCI adoption for organizations running on these platforms.
For reference, the parent project stargz-snapshotter already supports multiple runtimes including CRI-O, demonstrating that this architecture is feasible for lazy-loading snapshotters.

I do understand that the main usecase for SOCI was containerd (primary for AWS Fargate) #486 (comment) but I think it would really benefit organizations if support for other runtimes were added as well, atleast trying and matching the parent project stargz.

Use case:

• Running lazy-pulling in OpenShift environments
• Organizations standardized on CRI-O who want to benefit from SOCI's lazy loading capabilities

Questions:

• Is runtime-agnostic support (or CRI-O specifically) on the roadmap?
• Has the idea of separating the core SOCI FS from the snapshotter been explored further

[Shubhranshu153]

Hi @prafgup,

Thank you for the feature request. At the moment we dont have a contributor for the feature and haven't prioritized in the roadmap. We are happy to take contributions for the feature.

For now i have added to our backlog to triage.

[sondavidb]

Has the idea of separating the core SOCI FS from the snapshotter been explored further

This has been explored for a while, in an ideal world we would do it but given the current state of the FS it's gotten to be a messy problem trying to separate it. Not off the table though.