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

[JKHSDTV]

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.

[AverageMarcus]

It looks like the images pushed to Dockerhub are empty somehow.

✨ crane manifest nextcloud:35.0.0-apache
{"manifests":[],"mediaType":"application\/vnd.oci.image.index.v1+json","schemaVersion":2}%   

[jvnknvlgl]

I think this goes for all tags in the 35 range, I can at least confirm the issue for 35-fpm-alpine.

[playday3008]

Supposedly fixed 10 minutes ago

[Twilek-de]

Can confirm. Images are up and working.