Consider using OCI Image manifest fields like platform/arch/os instead of platform/arch tags
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 625
- Forks
- 103
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 1
Description
Current the use of tags for different architecture might not be the recommended way to distribute containers for different platforms/architecture/os. See https://docs.docker.com/engine/reference/commandline/manifest/#manifest-annotate
https://docs.docker.com/registry/spec/manifest-v2-2/
https://github.com/opencontainers/image-spec/blob/main/image-index.md
If enabled the container specification in docker-compose/kubernetes config won't have to worry about specifying the right architecture tag.
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the current architecture-tagging scheme and compare it with the linked Docker manifest and OCI image-index specifications. Done means platform, architecture, and OS are represented in OCI manifest fields so Docker Compose and Kubernetes configurations no longer need architecture-specific tags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100