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
On inspecting the Dockerfile, I found out that the go build stage for talaria is missing. Earlier versions of talaria used builder docker to run the go build command and get the talaria binary which will be copied to the final alpine image. But in the latest release version 0.7.7, the Dockerfile no longer performs the go build step and Makefile is also missing.
How are you making the go build?
If go build is to be run in the builder stage, the builder docker version of golang which is at 1.19 has to be updated to 1.21 to support the go version in go.mod?
The text was updated successfully, but these errors were encountered:
Thanks for the clarification. I am new to the goreleaser tool. While going through ci.yml file, it shows you are using the latest version of go to build the talaria binary. I think that clears my doubt regarding question 2.
Since go build is handled separately, is there a need for builder docker in Dockerfile?
Hi,
When running the docker build cmd
docker build -t talaria:v0.7.7 -f Dockerfile .
I am getting the following error
On inspecting the Dockerfile, I found out that the go build stage for talaria is missing. Earlier versions of talaria used builder docker to run the go build command and get the talaria binary which will be copied to the final alpine image. But in the latest release version 0.7.7, the Dockerfile no longer performs the go build step and Makefile is also missing.
How are you making the go build?
If go build is to be run in the builder stage, the builder docker version of golang which is at 1.19 has to be updated to 1.21 to support the go version in go.mod?
The text was updated successfully, but these errors were encountered: