use multistage build to create the container

[freym]

Build a static linked application inside a container

[BuJo]

I'm not sure if this interacts favorably with the current release process.
A binary is built in a github action with goreleaser, which builds binaries with built-in version information. It then takes the Dockerfile in the project root to build the resulting image.

As I see it, this would rebuild the go binary without adding the needed ldflags.

Unsure what the usecase is for having the Dockerfile compile the application. Is it to not install a full go sdk on a machine and still build the project?

[freym]

This makes it easier to build the image inside a CI Pipeline with tools like kaniko, which runs in a container. (https://github.com/GoogleContainerTools/kaniko)

[BuJo]

It would slim down the build-process for certain kinds of builds by one step, however all the caching that is possible by moving the actual build process into its own action/job would somehow have to be replicated and there's still the problem with missing build directives.

The project isn't using any docker packaging system directly, only through goreleaser. goreleaser can use docker or ko. However, we still have a kaniko based release pipeline in https://github.com/synyx/tuwat/blob/main/.gitlab-ci.yml#L89 from the time when it was built and released within a GitLab instance.

Neither one requires building the actual binary from within the Dockerfile, they all can provide the binary via ADD/COPY directives.

I'm still not sure what the actual use-case is here.