倉庫指標
- 星標
- (758 顆星)
- PR 合併指標
- (PR 指標待抓取)
描述
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) https://github.com/awslabs/soci-snapshotter/issues/486#issuecomment-1464665690 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