Open 06kellyjac opened 3 years ago
Im going to fix this as part of #250
I think both of are different issue because the go-releaser only changes the binary version that is present in the release page It won't change the binary present inside the container here
Yes I'm aware but I'm updating the version command so I'm fixing both separate issues at the same time.
The version will now list the version, full commit, source date epoch in RFC 3339 format, and unix epoch format
I'll either try plug those details into the docker build action or utilize goreleaser within the container builds
This issue is still happening:
$ docker run --rm kubesec/kubesec version
Unable to find image 'kubesec/kubesec:latest' locally
latest: Pulling from kubesec/kubesec
a0d0a0d46f8b: Pull complete
225a6626967c: Pull complete
50cb987b6fe2: Pull complete
404740fbf2d0: Pull complete
66230eef9706: Pull complete
7cd616b8ef56: Pull complete
Digest: sha256:1085be3c2494be9d8dc4884e7ceaf7a79fca650f02d1e36d6b1ac317e0495cb3
Status: Downloaded newer image for kubesec/kubesec:latest
version unknown
git commit unknown
build date unknown
Hi @06kellyjac, if you're interested, I can try to open a PR where I fix this issue by:
ldflags
argument of go build
, e.g. like this (Dockerfile in the question)Thanks for the offer but there are a couple other tweaks I want to make to the Dockerfiles so ill do that in 1 pr
Nice catch on that typo