Image adoptopenjdk/openjdk11-openj9:latest broken "no matching manifest for linux/amd64 in the manifest list entries"

[lquitadamo]

Hello,
i tried to pull the docker image and i get this error:

docker pull adoptopenjdk/openjdk11-openj9:latest
latest: Pulling from adoptopenjdk/openjdk11-openj9
no matching manifest for linux/amd64 in the manifest list entries

I try to pull a different tag ant it works:
docker pull adoptopenjdk/openjdk11-openj9:alpine
alpine: Pulling from adoptopenjdk/openjdk11-openj9
a0d0a0d46f8b: Pull complete
b9bfd4f1bdc2: Pull complete
9bb377e5716a: Pull complete
46761844314a: Pull complete
Digest: sha256:c232cbd9eaea69da89b7035622b153a07f27483bd58c79c7326ee6e99b3020aa
Status: Downloaded newer image for adoptopenjdk/openjdk11-openj9:alpine
docker.io/adoptopenjdk/openjdk11-openj9:alpine

It seems that "latest" build of adoptopenjdk/openjdk11-openj9 is broken.

This is my environment:

Docker Engine Version: v20.10.8

SO: Windows 10 (with WSL)

How can i fix this problem?

Thank you in advance.

[blackfenix]

Hi,

This issue existe in adoptopenjdk/openjdk8-openj9:latest tag

Doing a docker pull :

Step 1/18 : FROM adoptopenjdk/openjdk8-openj9 AS build-stage
latest: Pulling from adoptopenjdk/openjdk8-openj9
no matching manifest for linux/amd64 in the manifest list entries

It seems the "latest" tag is broken in several packages.

[CodingKoopa]

Running off of the same commit in my repo, my CI last succeeded on 2021/09/16, and has been failing since 2021/09/17. The failing build log is available here. This is using Docker buildx so the error message is different than that of the OP, but I believe it is the same issue.

[karianna]

You'll need to go to https://developer.ibm.com/languages/java/semeru-runtimes/ for updated container images.

[lquitadamo]

You'll need to go to https://developer.ibm.com/languages/java/semeru-runtimes/ for updated container images.

I don't understand. "IBM Semeru Runtimes" doesn't allow to pull docker images. How can I pull images from there?

[CodingKoopa]

So, in wanting to understand all this, I've went down the rabbit hole today.

This repository is deprecated, so I assume support is no longer being provided, hence this issue being closed. The reason why IBM Semeru Runtimes is the next step is a little complicated.

---

AdoptOpenJDK provided AdoptOpenJDK builds of OpenJDK with HotSpot, and also builds with OpenJ9. These builds have never been TCK tested.

With the migration from AdoptOpenJDK builds to Eclipse Temurin builds provided by the Eclipse Adoptium team, the maintainers have been licensed the Java SE TCK, but under the following stipulations:

• Adoptium most only release TCK certified builds.
• Adoptium must only test OpenJDK builds using Hotspot.

Thus, for legal reasons, despite Temurin being the most straightforward migration path from AdoptOpenJDK, Temurin builds with OpenJ9 do not exist.

To fill this hole, IBM now provides up to date builds of OpenJDK with OpenJ9, as the IBM Semeru Runtimes. IBM Semeru Runtime Open Edition, the permissively licensed, non-TCK tested version of the runtime, is the most direct replacement for OpenJ9 AdoptOpenJDK builds.

The infrastructure for building IBM Semeru Edition is in place, and there is an open pull request for it to be added to the set of Docker official images.

---

So, what can be done right now?

From the looks of it, the manifest for the deprecated AdoptOpenJDK OpenJDK image is devoid of pretty much all of the images:

$ docker buildx imagetools inspect adoptopenjdk/openjdk11-openj9
Name:      docker.io/adoptopenjdk/openjdk11-openj9:latest
MediaType: application/vnd.docker.distribution.manifest.list.v2+json
Digest:    sha256:31a500409bb0f6936a8d416ad2be72efbcdffe63a67f2af78f2190a635fbdb66

Manifests:
  Name:      docker.io/adoptopenjdk/openjdk11-openj9:latest@sha256:77fc0dd8ea293637ca1631752ffcb80dd9e3928328823c562838200ca4d4240d
  MediaType: application/vnd.docker.distribution.manifest.v2+json
  Platform:  linux/ppc64le

It seems as if there is no choice but to migrate to a new image, such as:

• The official AdoptOpenJDK images. This is just as deprecated as the unofficial images, and has different OS/architecture offerings, but at least can be pulled right now.
• The new Eclipse Temurin HotSpot OpenJDK images.
• One of the other Java Docker images, most of which too are HotSpot.

If you are able to wait, I would just hold on until the IBM Semeru Edition Docker images start getting pushed out, as that is the most similar replacement to what was broken here.

Further reading:

• Adoptium documentation issue
• Eclipse Temurin PR
• IBM Semeru Edition PR - this is the same PR we've been talking about, but if you have the time, read it! It's an interesting look at how legally encumbered Java remains, in some ways.

[AdamBrousseau]

I think the breakage was actually due to the OpenJ9 0.27.1 point release and subsequent Semeru update on Sept 16 only on plinux and aix platforms. This is why the manifest is broken from the automated AdoptOpenJDK build.
See my comment here eclipse-openj9/openj9#13534 (comment)
I expect when the October update is released late Oct, the AdoptOpenJDK unofficial docker builds will fix themselves. But ideally you should move to Official Semeru containers from DockerHub which are WIP as noted above. Or temporarily, unofficial images at u/ibmsemeruruntime.