NginxProxyManager / NginxProxyManager/nginx-proxy-manager
docker pull - no matching manifest for linux/arm/v8
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Hi,
Can't pull the latest jc21/nginx-proxy-manager:2.14.0 image.
docker pull jc21/nginx-proxy-manager:2.14.0
2.14.0: Pulling from jc21/nginx-proxy-manager
no matching manifest for linux/arm/v8 in the manifest list entries
2.13.7 is working.
docker pull jc21/nginx-proxy-manager:2.13.7
2.13.7: Pulling from jc21/nginx-proxy-manager
Digest: sha256:3c5acf6bc3125079906078d0cacec59130018bb32ed64092f7ce495edc68c5ec
Status: Downloaded newer image for jc21/nginx-proxy-manager:2.13.7
docker.io/jc21/nginx-proxy-manager:2.13.7
Thanks in advance.
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 inspecting how the 2.14.0 Docker image is built and published, then compare its manifest with the working 2.13.7 image for linux/arm/v8. Done means the 2.14.0 manifest includes linux/arm/v8 and the reported docker pull succeeds on that platform.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100