Docker Hub missing manifest for 3.19 amd64, and some other archs

[KamaranL]

After attempting to build an image with docker.io/library/alpine:3.19, I receive the following error:

#0 building with "default" instance using docker driver

#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 2.10kB done
#1 DONE 0.1s

#2 [internal] load metadata for docker.io/library/alpine:3.19
#2 ERROR: no match for platform in manifest: not found
------
 > [internal] load metadata for docker.io/library/alpine:3.19:
------
Dockerfile:1
--------------------
   1 | >>> FROM docker.io/library/alpine:3.19
   2 |     
   3 |     LABEL \
--------------------
ERROR: failed to solve: docker.io/library/alpine:3.19: failed to resolve source metadata for docker.io/library/alpine:3.19: no match for platform in manifest: not found

[^1] Verified on Docker Hub that the amd64 arch (as well as some others) are missing for 3.19, but not 3.18 or 3.20[^2].

[^1]:

[^2]: Verified I could build with 3.18 and 3.20, but the image I need to build has packages that currently only work in 3.19.

[ls-justin-bull]

Yeah this is also breaking my builds.

no matching manifest for linux/amd64 in the manifest list entries

Using tag: alpine:3.20

Oddly enough, linux/amd64 is supported for tag 3.20.3

[KamaranL]

Oddly enough, linux/amd64 is supported for tag [3.20.3]

I tried using 3.20, but most packages I'm installing during the build are either not available or they're renamed with their version appended to it. E.g. compiling StrongSwan from source breaks in 3.20

[JakeWarner]

My guess is that these builds tried to go to DockerHub during the maintenance window earlier today -- auth, etc were failing for ~20 minutes.

[ls-justin-bull]

@KamaranL It looks like the last release failed for some reason, potentially related to the outage mentioned by @JakeWarner

I see that 3.19.3 supports linux/amd64, I would try that.

[KamaranL]

I see that 3.19.3 supports linux/amd64, I would try that.

Wow. I feel green. 🤦🏽‍♂️

THAT worked. 😅

[ls-justin-bull]

Looks like the last update fixed the issue