Closed twocs closed 1 year ago
Possibly a bit of a moot point because golang 1.19 can build version 1.18, although there is a lack of clarity on the specific version when doing that.
That's a perfectly reasonable request :)
We're still working on our policy wrt older versions across the board for our images.
In general, we want to encourage regular updating as it's the only way to stay free of vulnerabilities. In the 1.18 case it's still actively updated, so I'm leaning towards supporting it currently.
Possibly a bit of a moot point because golang 1.19 can build version 1.18, although there is a lack of clarity on the specific version when doing that.
To correct myself, building 1.18 using 1.19 does not work. It applies the 1.19 struct with the extra field instead of the 1.18 struct.
I was looking for something similar, specifically cgr.dev/chainguard/go:1.19
. Any plans to tag specific go
minors?
@gerhard I'm sorry this isn't more obvious right now, but that image does exist:
docker pull cgr.dev/chainguard/go:1.19
and
docker pull cgr.dev/chainguard/go:1.19.4
We have an update coming on what major and minor versions of images we will be supporting going forward (across all images)
This should work now. Apologies for the delay.
docker pull cgr.dev/chainguard/go:1.18
Feels a bit selfish to ask for a go 1.18 version, and was looking into building my own image.
But then I noticed that Apko itself is currently built with go 1.18. Would it be possible to have a 1.18 tagged version? (We are considering upgrading soon, but there is a very minor issue that 1.19 now has an extra OmitHost bool field in the url.URL payload).
Go version 1.18 wil continue to be supported until the 1.20 release, likely around February 2023. Please close this issue if there is any good reason that go version 1.18.6 is not supported.