Dapper Build tool: consistent builds with docker
This articles shows how to use the dapper build tool from Rancher Labs.
The basic idea is to use Docker containers, copy* your source files into the container environment, then compile, then copy the build artefacts out.
(* on Linux you can also use the mount mode to avoid copying the files.)
How to use it: you start by installing Go so you can compile Dapper. I know, I know, but if you will humor me, I will convince you that Go is the last programming language compiler you will need to install on your host.
- Install Go: https://go.dev/dl/
- Build Dapper:
go install github.com/rancher/dapper@latest
- Make a Dockerfile.dapper
Dockerfile.dapper is a regular Dockerfile. As an example, create one with your favorite programming language
you don’t have installed, let’s say it’s OCaml.
Then you can open a shell in that container by running
dapper -s. Or if
you wanted to run it as a one-liner, try running the opam compiler:
% dapper opam --version ...(docker build output)... 2.0.10
Doesn’t Nix do something like that? Why yes it does, although it takes some getting used to the functional programming language used to define nix packages. An obvious advantage of the dapper approach is familiarity of shell scripts and Dockerfiles. If your team is familiar with these things then Dapper will be a good fit for acheiving reproducible builds.
I haven’t done enough of a deep dive on nix to have much of an opinion on how it compares to the dapper approach. If you are interested, post some comments below and I’ll do comparison of Nix and Dapper.
On the Go language, one of it’s virtues is producing self-contained single binary executable files. Programs written in Go can be a single file you download and run. It’s great. Also a large and quickly growing number of programs are written in Go:
- Docker (Linux processes running in control groups with isolated, immutable layered filesystems)
- Kubernetes (Control system for clusters of machines running docker containers)
- Rancher (Kubernetes cluster manager)
- Harvester (Hyperconverged infrastructure)
- etcd (Distributed high-availability key-value store)
- osin (OAuth2 server library)
Go binaries also don’t need a virtual machine (like node/python/java/…etc). So Go programs can be really fast, compared to scripting languages like Python.
So, installing Go means you can build Dapper, and Dapper lets you achieve reproducible builds so you can say “works on my machine” and it will really work on another person’s machine.