You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ syft -q golang:tip | grep ^go
$ docker run -it --rm golang which go
/usr/local/go/bin/go
$ docker run -it --rm golang:tip go version
go version devel go1.25-d524e1e Sun Feb 16 07:23:13 2025 -0800 linux/amd64
$ docker run -it --rm golang:tip strings /usr/local/go/bin/go | grep -e '1\.25'
devel go1.25-d524e1e Sun Feb 16 07:23:13 2025 -0800
3devel go1.25-d524e1e Sun Feb 16 07:23:13 2025 -0800
The text was updated successfully, but these errors were encountered:
❯ docker run -it --rm golang:tip go version -m /usr/local/go/bin/go
/usr/local/go/bin/go: devel go1.25-fba83cd Sun Feb 23 12:04:15 2025 -0800
path cmd/go
build -buildmode=exe
build -compiler=gc
build CGO_ENABLED=0
build GOARCH=arm64
build GOOS=linux
build GOARM64=v8.0
Dev question: is that version the version of the toolchain that built the Go CLI, or the version of the Go CLI? If we find the string devel go1.25-fba83cd via regex or examining buildInfo, is that the right string? Or are the two versions the same, and we're comfortable relying on the coincidence that the Go version used to build tip is the Go version tip?
What would you like to be added:
Support golang tip image in binary detection
Additional context:
The text was updated successfully, but these errors were encountered: