Fallback platforms feature
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Description
Many container images I uses are available for multiple platforms, most notably linux/amd64 and linux/arm64. On a current macbook any docker image pull will pull the linux/arm64 image - if that exists.
If that does not exist, pulling will fail with an error like:
no matching manifest for linux/arm64/v8 in the manifest list entries
I have enabled Rosetta on the macbook, will allows me to run linux/amd64 images. In almost all cases running a non-native linux/amd64 image is preferable over not being able to run the image at all.
So, if a normal image pull fails because there is not linux/arm64 image, then I will always have to manually add --platform linux/amd64 to the command.
It would be great if there was a optional/configurable list of fallback platforms that would be tried if the native platform isn't available.
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
The issue names no files, tests, or entry points. Start by tracing Docker CLI image-pull platform selection and the existing --platform handling, then determine where an optional fallback list belongs. Done means a configurable ordered list is tried when the native platform has no matching manifest, with tests covering fallback selection and failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100