containerd / containerd/accelerated-container-image

Support loading container images from a secondary disk attached to a kubernetes node

Open
#283 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Go
Stars
470
Forks
87
Avg merge
2d 21h
Merged PRs (30d)
5

Description

### What is the version of your Accelerated Container Image

_No response_

### What would you like to be added?

Have the option to load container images which are pre-loaded on a secondary disk that is attached to the node.

Overlaybd needs to:
1) use container images pre-loaded in the secondary disk (format and paths to be determined),
2) provide the same on-demand image loading capabilities, based on network availability.

### Why is this needed for Accelerated Container Image?

1) Very large container images that need most data to be loaded at the start (particularly for deep learning workloads):
Workloads like inference with large language models need most of the container image loaded to memory, before serving traffic. In these cases, having the ability to attach a secondary disk to the node can speed up the process. If there are updates to the container image, then we still need to be able to only download the difference in content needed, and in an on-demand manner.

2) Air-gapped nodes:
If there are networking restrictions in downloading from a remote registry because of security reasons, for instance, then being able to use container images attached from a secondary disk will be useful.

### Are you willing to submit PRs to contribute to this feature?

- [X] Yes, I am willing to implement it.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.