-
Notifications
You must be signed in to change notification settings - Fork 18.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[24.0] update to go1.20.13#47054
[24.0] update to go1.20.13 #47054
Conversation
Oh! It's failing because it's still using alpine 3.17, which is no longer published (EOL?) |
Oh! Dang.... and that's in the BuildKit repository, not here 😞 Here we go again. Changing my middle-name to "Shaver of Yaks and opener of cans of worms" |
1937ee2
to
d641cf0
Compare
Looks like the BuildKit 0.11 Dockerfile is still using go1.19 (which we override using |
Ah, dang; still changes needed; looks like the script doesn't pass
|
d641cf0
to
4043548
Compare
vendor.mod
Outdated
@@ -56,7 +56,7 @@ require ( | |||
github.com/klauspost/compress v1.17.2 | |||
github.com/miekg/dns v1.1.43 | |||
github.com/mistifyio/go-zfs/v3 v3.0.1 | |||
github.com/moby/buildkit v0.11.7-0.20230908085316-d3e6c1360f6e // IMPORTANT: when updating, also update the version in builder/builder-next/worker/worker.go | |||
github.com/moby/buildkit v0.11.7-0.20240110143849-d08077628de0 // IMPORTANT: when updating, also update the version in builder/builder-next/worker/worker.go |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated the BuildKit version so that we can use ALPINE_VERSION
in CI (GHA uses the same commit to test buildkit);
- full diff: moby/buildkit@d3e6c13...d080776
NOOOOOOO! Now we have
|
See the docker/cli repo where we had the same issue; |
full diff: moby/buildkit@d3e6c13...435cb77 The 0.11 branch of buildkit defaults to go1.19 (EOL), and Alpine 3.17 (EOL). We already set GO_VERSION to override the go version to use go1.20, but the Dockerfile also has a ALPINE_VERSION build-arg, so let's override that as well to prevent the build from failing: Dockerfile:39 -------------------- 37 | 38 | # go base image 39 | >>> FROM --platform=$BUILDPLATFORM golang:${GO_VERSION}-alpine${ALPINE_VERSION} AS golatest 40 | 41 | # git stage is used for checking out remote repository sources -------------------- ERROR: failed to solve: golang:1.20.13-alpine3.17: docker.io/library/golang:1.20.13-alpine3.17: not found Error: Process completed with exit code 1. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
go1.20.13 (released 2024-01-09) includes fixes to the runtime and the crypto/tls package. See the Go 1.20.13 milestone on our issue tracker for details: - https://github.com/golang/go/issues?q=milestone%3AGo1.20.13+label%3ACherryPickApproved - full diff: golang/go@go1.20.12...go1.20.13 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
4043548
to
542fc0b
Compare
update buildkit and set ALPINE_VERSION=3.18
full diff: moby/buildkit@d3e6c13...435cb77
The 0.11 branch of buildkit defaults to go1.19 (EOL), and
Alpine 3.17 (EOL).
We already set GO_VERSION to override the go version to
use go1.20, but the Dockerfile also has a ALPINE_VERSION
build-arg, so let's override that as well to prevent the
build from failing:
full diff: moby/buildkit@d3e6c13...435cb77
update to go1.20.13
go1.20.13 (released 2024-01-09) includes fixes to the runtime and the crypto/tls package. See the Go 1.20.13 milestone on our issue tracker for details:
- What I did
- How I did it
- How to verify it
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)