Summary
The azul-zulu image is part of the Official Images program, but it does not appear to be synced to the AWS Public ECR mirror (public.ecr.aws/docker/library/). Other Official Java images such as eclipse-temurin and openjdk are present there.
Reproduction
azul-zulu — repository does not exist on Public ECR:
$ podman pull public.ecr.aws/docker/library/azul-zulu:8-jre-headless-alpine
...
Error: ... name unknown: The repository with name 'library/azul-zulu' does not
exist in the registry with id 'docker'
For comparison, a peer Official Image works fine:
$ podman pull public.ecr.aws/docker/library/eclipse-temurin:8-jre
... (succeeds)
Tag listing via the Public ECR API (with an anonymous token) confirms:
docker/library/eclipse-temurin → 200
docker/library/openjdk → 200
docker/library/azul-zulu → 404
Impact
Users pulling from public.ecr.aws (common in regions where Docker Hub is slow or rate-limited) cannot use azul-zulu at all and must fall back to Docker Hub, unlike the other Official Images which are mirrored.
Request
Could azul-zulu be added to the Public ECR sync set? Related prior issue: #13152.
Summary
The
azul-zuluimage is part of the Official Images program, but it does not appear to be synced to the AWS Public ECR mirror (public.ecr.aws/docker/library/). Other Official Java images such aseclipse-temurinandopenjdkare present there.Reproduction
azul-zulu— repository does not exist on Public ECR:For comparison, a peer Official Image works fine:
Tag listing via the Public ECR API (with an anonymous token) confirms:
docker/library/eclipse-temurin→200docker/library/openjdk→200docker/library/azul-zulu→404Impact
Users pulling from
public.ecr.aws(common in regions where Docker Hub is slow or rate-limited) cannot useazul-zuluat all and must fall back to Docker Hub, unlike the other Official Images which are mirrored.Request
Could
azul-zulube added to the Public ECR sync set? Related prior issue: #13152.