35-apache: Pulling from library/nextcloud - no matching manifest for linux/amd64 in the manifest list entries

Open
#2,601 4 comments 22 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
64/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
docker
Domain
devops

Research direction

Start by reproducing the documented docker pull nextcloud:35 and nextcloud:35-apache failures for linux/amd64, then compare those manifests with the latest alias and the other current 35 tags. Done means the affected 35 tags have a matching linux/amd64 manifest and Docker Hub's aliases point consistently to the intended images.

Written by the indexing model from the issue text.

Description

0. Needs triage bug

I understand 35 just hit, and I am not complaining it 'isn't ready yet'; I am reporting a mismatch in the Dockerhub tag documentation. It seems something with the tagging went wrong for 35:

$ docker pull nextcloud:latest
latest: Pulling from library/nextcloud
6310eb16bf42: Already exists 
9e5d43abcc54: Pull complete 
[...]
Digest: sha256:9558b1cea2f5fb992a78ea6ed93890922ec623e0a853741303e6369e54d3b902
Status: Downloaded newer image for nextcloud:latest
docker.io/library/nextcloud:latest

According to Dockerhub, latest should currently be an alias to 35 and 35-apache, but:

$ docker pull nextcloud:35
35: Pulling from library/nextcloud
no matching manifest for linux/amd64 in the manifest list entries
$ docker pull nextcloud:35-apache
35-apache: Pulling from library/nextcloud
no matching manifest for linux/amd64 in the manifest list entries

It seems all of the current 35 tags are affected. Dockerhub shows latest being an alias for the range, but they seem to point at different things.

Dominant language
Shell
Stars
7.4k
Forks
1.9k
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nextcloud/docker

All issues in nextcloud/docker

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.