Latest published image of Go 1.25 and Go 1.26 do not have AMD64 platform manifest

[pbettadapura]

Microsoft build of Go version

go 1.25, go 1.26

What is your operating system and platform?

Linux AMD64

Output of go env in your module/workspace:

set AR=ar
set CC=gcc
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_ENABLED=1
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set CXX=g++
set GCCGO=gccgo
set GO111MODULE=
set GOAMD64=v1
set GOARCH=amd64
set GOAUTH=netrc
set GOBIN=
set GOCACHE=C:\Users\pbettadapura\AppData\Local\go-build
set GOCACHEPROG=
set GODEBUG=
set GOENV=C:\Users\pbettadapura\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFIPS140=off
set GOFLAGS=
set GOGCCFLAGS=-m64 -mthreads -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=C:\Users\PBETTA~1\AppData\Local\Temp\go-build3134138984=/tmp/go-build -gno-record-gcc-switches
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMOD=Q:\src\Singularity\src.aksflex\src\common\observability\diagnostics-helper\go.mod
set GOMODCACHE=C:\Users\pbettadapura\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\pbettadapura\go
set GOPRIVATE=
set GOPROXY=direct
set GOROOT=C:\Users\pbettadapura\go\pkg\mod\golang.org\toolchain@v0.0.1-go1.25.0.windows-amd64
set GOSUMDB=sum.golang.org
set GOTELEMETRY=local
set GOTELEMETRYDIR=C:\Users\pbettadapura\AppData\Roaming\go\telemetry
set GOTMPDIR=
set GOTOOLCHAIN=auto
set GOTOOLDIR=C:\Users\pbettadapura\go\pkg\mod\golang.org\toolchain@v0.0.1-go1.25.0.windows-amd64\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.25.0
set GOWORK=
set PKG_CONFIG=pkg-config

What did you do?

docker pull mcr.microsoft.com/oss/go/microsoft/golang:1.25

What did you see happen?

Error response from daemon: no matching manifest for linux/amd64 in the manifest list entries: no match for platform in manifest: not found

What did you expect to see?

Docker pull successful

[qmuntal]

We have republished the images with the correct manifests, and the issue should now be resolved. Could you please confirm at your convenience that everything is working as expected?

Apologize for any inconvenience caused.

[pbettadapura]

yes its resolved, thank you!

[sebdau]

@qumuntal can you please share an RCA and mention potential repair items?

[qmuntal]

This is the latest status: #2313 (comment).

We are continuing to work with the .NET Docker infrastructure team to understand the root cause. We will share the findings once the RCA is complete.

In the meantime, we have implemented the following mitigations:

• Paused automatic image publishing pipelines. Until the retrospective is completed, all publishing will be manually triggered and validated to ensure the issue does not recur.
• Hardened the Docker image tooling along the code paths involved in the incident (see Write build matrix variables directly to stdout dotnet/docker-tools#2125).

We will also be rolling out an additional safeguard: an automated check that will cause the publishing process to fail if any platform manifests are missing (see dotnet/docker-tools#2126).