awslabs/soci-snapshotter

[FEATURE] CRI-O runtime support

Open

#1,854 opened on Jan 29, 2026

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (88 forks)auto 404
featurehelp wanted

Repository metrics

Stars
 (758 stars)
PR merge metrics
 (PR metrics pending)

Description

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

Contributor guide

Research direction
Study how stargz snapshotter integrates with CRI O (e.g., via CRI O's runtime plugin interface or by implementing a CRI O snapshotter adapter). Understand the SOCI snapshotter architecture and identify the points where containerd specific code is used. Plan to abstract or create a plugin interface for different runtimes.
Tech stack
go
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GocontainerdCRI O
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50