docker build with OCI layouts does not preserve OCI annotations set on individual layers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4.5k
- Forks
- 682
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 29
Description
Description
I am using docker build
The FROM image is in OCI format
The FROM image has OCI annotations on the OCI manifest and in each OCI layer
I am using containerd backend and output to OCI format as well
The produced image tarball did not preserve OCI annotations on neither the OCI manifest nor the OCI layer
Please consider preserving OCI image.layer annotations during such builds
Note, these are different than the image.manifest level annotations
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with docker build using a FROM OCI image, the containerd backend, and OCI output. Trace the containerd backend's OCI output path; the payload names no source file or test. Done means the produced OCI tarball retains both manifest-level and individual image.layer annotations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100