You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a MacBook (Apple M1 Pro) and trying to build an image FROM websphere-liberty:23.0.0.4-full-java8-ibmjava.
However, I'm getting the below error
` => ERROR [internal] load metadata for docker.io/library/websphere-liberty:23.0.0.4-full-java8-ibmjava 1.3s
[internal] load metadata for docker.io/library/websphere-liberty:23.0.0.4-full-java8-ibmjava:
Dockerfile:1
1 | >>> FROM websphere-liberty:23.0.0.4-full-java8-ibmjava
ERROR: failed to solve: websphere-liberty:23.0.0.4-full-java8-ibmjava: no match for platform in manifest sha256:77614c00802348dc0f7b82992174d1259d7ca2f1adf78c4d9237e2de16c0dca4: not found`
I have also tried just only FROM websphere-liberty, but getting the same error.
@carlosperri Liberty images use the IBM Java images (available here) as the base image. IBM Java 8 images don't provide arm64, hence Liberty images with IBM Java 8 are not available for arm64. However, Semeru OpenJ9-based images are available for arm64 (i.e. websphere-liberty:23.0.0.4-full-java11-openj9).
I have a MacBook (Apple M1 Pro) and trying to build an image
FROM websphere-liberty:23.0.0.4-full-java8-ibmjava
.However, I'm getting the below error
` => ERROR [internal] load metadata for docker.io/library/websphere-liberty:23.0.0.4-full-java8-ibmjava 1.3s
Dockerfile:1
1 | >>> FROM websphere-liberty:23.0.0.4-full-java8-ibmjava
ERROR: failed to solve: websphere-liberty:23.0.0.4-full-java8-ibmjava: no match for platform in manifest sha256:77614c00802348dc0f7b82992174d1259d7ca2f1adf78c4d9237e2de16c0dca4: not found`
I have also tried just only
FROM websphere-liberty
, but getting the same error.On official docker image site (https://hub.docker.com/_/websphere-liberty) I see it supports several architectures, including arm64.
Why am I not able to pull the image?
Thanks!
The text was updated successfully, but these errors were encountered: