rss resume / curriculum vitae linkedin linkedin gitlab github twitter mastodon instagram
Building Go programs using Makefiles
Dec 15, 2016

The idiomatic way of installing binaries in Go is using go install <path-to-binary>, for example something like:

go install

will build and then install the hello program into your $GOPATH/bin (of course assuming you previously go get it), and that is great if that’s what you’re looking for. However, if you’re like me and you use small docker images for running your programs on production, then you need to have a Makefile for building all of them consistently; of course this does not mean you can’t have the best of both worlds.

Let’s assume you have a collection of binaries, following the common pattern of defining a package, this package is then used by all the programs in cmd/, so you would have something like this:

$ ls -d *.go */*/*
cmd/hello/main.go     cmd/something/main.go something.go

I created a small repo containing this example, so you can follow along; using that said repo you could execute:

go install

That will build and install both programs:

$ which hello
$ which something

What is needed next is to create a Makefile for building all our binaries in a Docker image, then copy those to the static and final image which in the end will be used for the final container. You can follow the Makefile from the repo, it literally contains the following:


PROGRAMS=hello something

.PHONY: clean

default: build

	docker run --tty ${NAMESPACE}:build /bin/true && \
		docker cp `docker ps -q -n=1`:/$@ . && \
		docker rm `docker ps -q -n=1`

	docker build --tag ${NAMESPACE}:build --file ./ .

build: builddocker $(PROGRAMS)
	docker run --tty ${NAMESPACE}:build /bin/true && \
		docker rm `docker ps -q -n=1` && \
		docker build --rm --tag ${NAMESPACE}:latest --file ./Dockerfile.static .

	for program in $(PROGRAMS) ; do \
		CGO_ENABLED=0 GOOS=linux go build --ldflags="-s" -a -installsuffix cgo \
			-o $${program} ./go/src/$${program}; \

The important bit is the PROGRAMS variable, which is currently hardcoded to the existing directories in cmd/ that represent the Go programs to be built. Could we get this variable from the output of a simple ls? Yes, definitely.

Another important part of this build is the static Dockerfile:

# vim: set syntax=dockerfile:
FROM tianon/true

MAINTAINER Mario Carrion "info@xyz"

COPY ["hello", \
      "something", \

ENTRYPOINT ["/app/hello"]
CMD []

Again, similar to the Makefile it hardcodes the files to be copied.

In the end those are the two caveats of this process, you have to explicitly add the programs to both files in order to correctly build the whole thing, I’ll think about a better alternative and as soon as I have a fix for this, I’ll blog about it for sure.

Back to posts