Repository navigation
Published tags missing from Hub UI/API while registry serves them (iokaio/munarium) #2533
Description
Problem description
Docker Hub's website and metadata API do not reflect successfully published tags for the public repository iokaio/munarium, while Docker Registry v2 lists and serves them. Please investigate and reconcile the repository's Hub tag metadata with the registry.
Expected behavior
Hub should display 1.1.0, 1.1, 1.1.0-rc.1, and sha-8564588f859f1b41aa09f98423023e172239563d. The metadata for latest should identify the newly published release.
Actual behavior
Registry v2 lists nine tags, including the four above. Anonymous manifest requests for 1.1.0 and latest succeed and identify:
sha256:0e8a82c978a941380df68a55fe9346123cbd7f24c6375ba0b70a00986d152cd3
A Docker pull succeeded:
$ docker pull --platform linux/amd64 docker.io/iokaio/munarium:1.1.0
1.1.0: Pulling from iokaio/munarium
Digest: sha256:0e8a82c978a941380df68a55fe9346123cbd7f24c6375ba0b70a00986d152cd3
Status: Downloaded newer image for iokaio/munarium:1.1.0
However, both Hub API routes list only five old tags:
- https://hub.docker.com/v2/repositories/iokaio/munarium/tags?page_size=100
- https://hub.docker.com/v2/namespaces/iokaio/repositories/munarium/tags?page_size=100
The listed tags are latest, 1.0, 1.0.0, 1.0.0-rc.1, and sha-154b9c4f33b13a9f58a2229f578c0d7644410449.
https://hub.docker.com/v2/repositories/iokaio/munarium/tags/1.1.0/ returns HTTP 404.
Hub metadata for latest still reports the previous digest and push time:
digest: sha256:9f5cd5dec2f52cef26aabce625ace1390164e4930c93b5cc0d2177806b498d4c
last_updated: 2026-09-06T04:32:03.363006Z
The public repository page and repository management page show the same old tags, including in an Edge InPrivate session. Fresh query strings and Cache-Control: no-cache did not resolve the API discrepancy.
Publication and recovery attempt
Original publication used regctl v0.11.6 image import and image copy. Stable promotion completed at 2026-09-08T20:14:58Z.
We subsequently re-published the exact existing index using Docker's own tooling:
docker buildx imagetools create --progress plain \
--tag docker.io/iokaio/munarium:1.1.0 \
--tag docker.io/iokaio/munarium:1.1 \
--tag docker.io/iokaio/munarium:latest \
docker.io/iokaio/munarium@sha256:0e8a82c978a941380df68a55fe9346123cbd7f24c6375ba0b70a00986d152cd3Docker reported successful pushes for all three tags. Subsequent registry verification confirmed the same expected digest for all three, but Hub's metadata still showed the old five tags.
The index uses application/vnd.oci.image.index.v1+json and contains:
- linux/amd64:
sha256:fab152bd2703fa845aa6cdd10e704d968df211d0b4cc3b58b088d073d73ec86f - linux/arm64:
sha256:196e4dc26acaa5a25046a6221dc4072760092bee70a8b9606ce32f0f5e723c97 - Two attestation manifests with unknown/unknown platforms, matching the structure used by the visible 1.0.0 release.
Both architecture images were pulled and tested successfully (ARM64 under Docker Desktop emulation). Prior 1.0.0 and 1.0 tags remain unchanged. No rebuild, manifest conversion, tag deletion, or signature change was performed during the refresh.
Debug information
- Repository: https://hub.docker.com/r/iokaio/munarium
- Publisher namespace:
iokaio - Observation date: 2026-09-08, following the 20:14:58 UTC stable promotion
- Host: Windows, Docker Desktop in Linux container mode
- Docker client: 29.5.2
- Buildx: v0.34.0-desktop.1
- Browser: Microsoft Edge, including InPrivate (exact browser version not captured)
- Docker status reported all systems operational when checked. The root cause is not confirmed.
- Public release: https://github.com/iokaio/munarium/releases/tag/v1.1.0
The discrepancy also reproduces with direct public HTTP API requests and does not require a local Docker daemon. No credentials or private host diagnostics are included.
Task list
- This is not a security issue.
- Searched existing issues; no applicable open report for this repository was found.
- Subscription status is not asserted in this report.
Activity
github-actions commentedon Sep 8, 2026
Thank you for your feedback 👍.
Our team will review your issue shortly.
In the meantime, feel free to provide as many details as possible, as this will speed up the resolution.
If you need assistance rather than providing feedback, please contact the Docker support team via https://hub.docker.com/support/contact for a prompt response, and close this issue.
tylerje commentedon Sep 8, 2026
Additional evidence from the repository owner's browser: Image Management does show the new release, while the General/Tags views and public metadata remain stale.
At https://hub.docker.com/repository/docker/iokaio/munarium/image-management?sortField=last_pushed&sortOrder=desc the screenshot shows:
sha256:0e8a82c978a9, matching the approved release index.1.1,1.1.0, and1.1.0-rc.1, plus two additional collapsed tags.linux/arm64child with digest prefixsha256:196e4dc26aca, matching the release child.The repository header on the same page still says "Last pushed 3 days ago". A fresh public Hub tags API check still returns only the five old tags, with
latestidentifying the prior9f5cd5...digest.This narrows the discrepancy: the release is visible in Image Management as well as the registry, but not in the General/Tags/public metadata views. The issue remains reproducible.