golang:1.22-alpine3.19 amd64
rez1dent3 opened this issue · comments
Hello. I see that the amd64 architecture should be available for the golang:1.22-alpine3.19 image, but it is not.
Tags: 1.22.0-alpine3.19, 1.22-alpine3.19, 1-alpine3.19, alpine3.19, 1.22.0-alpine, 1.22-alpine, 1-alpine, alpine
Architectures: amd64, arm32v6, arm32v7, arm64v8, i386, ppc64le, s390x
GitCommit: 893a2c96ba6154de2ad3663d087998bfda0a04e9
Directory: 1.22/alpine3.19
Tags: 1.22.0-alpine3.18, 1.22-alpine3.18, 1-alpine3.18, alpine3.18
Architectures: amd64, arm32v6, arm32v7, arm64v8, i386, ppc64le, s390x
GitCommit: 893a2c96ba6154de2ad3663d087998bfda0a04e9
Directory: 1.22/alpine3.18
https://hub.docker.com/_/golang/tags?page=1&name=1.22-alpine3.19
https://hub.docker.com/_/golang/tags?page=1&name=1.22-alpine3.18
The same issue is with the regular 1.22 tag: https://hub.docker.com/layers/library/golang/1.22/images/sha256-8ad949991d4bcac2fff5a1dbfa77d4a92840f42d32704a1c26254b82faf6d738?context=explore (no linux/amd64 variant).
It is because the image is being built https://doi-janky.infosiftr.net/job/multiarch/job/amd64/job/golang/
The job is waiting for an executor.
Still waiting to schedule task
Waiting for next available executor on ‘[multiarch-amd64](https://doi-janky.infosiftr.net/computer/multiarch%2Damd64/)’
https://doi-janky.infosiftr.net/job/multiarch/job/amd64/job/golang/565/console
I believe you mean https://doi-janky.infosiftr.net/job/multiarch/job/amd64/job/golang/565/console (565, not 564)
Job has finally succeeded. Time to resume working 😆
Yep, builds were still in progress.