As Garden Linux adopter, I want to be able to pull my image of choice via Open Container Initiative (OCI)[1] Image Specification (image-spec) container layers, served for me from public registry.
[ ] Integration of tooling into release build pipelines of Garden Linux, so that Garden Linux release artefacts can be incrementally be attached to an OCI-image until it reaches a defined state of "final" including cryptographic signatures
Epic: OCI Initial Delivery
Scope
As Garden Linux adopter, I want to be able to pull my image of choice via Open Container Initiative (OCI)[1] Image Specification (image-spec) container layers, served for me from public registry.
[1] See https://opencontainers.org/about/overview/
High Level Architecture
The Architecture Diagram above shows the existing Garden Linux pipeline state, and the OCI extensions for the pipelines. Architectural decisions are:
Requirements
Architectural alignments and discussions
Before the initial implementation, a request for discussion was prepared. Summary of discussion is included in the RFD linked above.
Definition of done
Tasks
September
Bugs
Enhancements
August
Bugs
Enhancements
July
June