composectl currently maintains its own OCI content store and then imports images into the container runtime.
On systems using containerd as the image backend, this can result in multiple copies of the same image data being stored on disk:
- composectl content store
- containerd content store
- containerd snapshotter storage
This is particularly costly on storage-constrained edge devices and for large application or AI/ML images.
Investigate using containerd as the primary OCI content store and streaming image content directly into it, eliminating the need for a separate persistent content store in composectl.
If the investigation determines that this approach is feasible and provides meaningful benefits, implement a prototype to validate the architecture and quantify storage savings.
Expected benefits:
- Reduced storage utilization
- Less duplicate image data
- Better alignment with containerd architecture
- Improved support for large artifacts on edge devices
composectlcurrently maintains its own OCI content store and then imports images into the container runtime.On systems using containerd as the image backend, this can result in multiple copies of the same image data being stored on disk:
This is particularly costly on storage-constrained edge devices and for large application or AI/ML images.
Investigate using containerd as the primary OCI content store and streaming image content directly into it, eliminating the need for a separate persistent content store in composectl.
If the investigation determines that this approach is feasible and provides meaningful benefits, implement a prototype to validate the architecture and quantify storage savings.
Expected benefits: