To build the docker image in development, use
docker build -f docker/rust.dockerfile -t ballistacompute/ballista-rust:latest .
This uses a multi-stage build, on which the build stage is called builder.
Our github has this target cached, that we use to speed-up the build time:
export BUILDER_IMAGE=docker.pkg.github.com/ballista-compute/ballista/ballista-rust-builder:main
docker login docker.pkg.github.com -u ... -p ... # a personal access token to read from the read:packages
docker pull $BUILDER_IMAGE
docker build --cache-from $BUILDER_IMAGE -f docker/rust.dockerfile -t ballista:latest .
will build the image by re-using a cached image.
This project often requires testing on kubernetes. For this reason, we have a github workflow to push images to github's registry, both from this repo and its forks.
The basic principle is that every push to a git reference builds and publishes a docker image.
Specifically, given a branch or tag ${REF},
docker.pkg.github.com/ballista-compute/ballista/ballista-rust:${REF}is the latest image from $REFdocker.pkg.github.com/${USER}/ballista/ballista-rust:${REF}is the latest image from $REF on your fork
To pull them from a kubernetes cluster or your computer, you need to have a personal access token with scope read:packages,
and login to the registry docker.pkg.github.com.
The builder image - the large image with all the cargo caches - is available on the same registry as described above, and is also available in all forks and for all references.
Please refer to the rust workflow and rust dockerfile for details on how we build and publish these images.
If you do not aim to run this in docker but any linux-based machine, you can get the latest binary from a docker image on the registry: the binary is statically linked and thus runs on any linux-based machine. You can get it using
id=$(docker create $BUILDER_IMAGE) && docker cp $id:/executor executor && docker rm -v $id