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
we were using this and today can no longer pull the image, our builds are failing because of this
riteshadval$ docker pull arm32v7/openjdk:8-jre
8-jre: Pulling from arm32v7/openjdk
no matching manifest for unknown in the manifest list entries
are we suppose to now use arm32v7/openjdk:8-jre-stretch, thats seems to be ok to download but removing tag like arm32v7/openjdk:8-jre not a good idea when people are using images in wild.
The text was updated successfully, but these errors were encountered:
Looks like the 8 variants have been failing to build on arm32v7 for a while: 😞
. . .
There's something quirky going on with the Debian package we're pulling from, unfortunately (and it seems to not affect amd64 for whatever reason).
we were using this and today can no longer pull the image, our builds are failing because of this
riteshadval$ docker pull arm32v7/openjdk:8-jre
8-jre: Pulling from arm32v7/openjdk
no matching manifest for unknown in the manifest list entries
are we suppose to now use arm32v7/openjdk:8-jre-stretch, thats seems to be ok to download but removing tag like arm32v7/openjdk:8-jre not a good idea when people are using images in wild.
The text was updated successfully, but these errors were encountered: