Reproducible build
This section shows how to build the Contrast release artifacts from a release tag and check that they're identical to the published ones.
Applicability
Optional, for verifying that a Contrast release was built from the released source.
Prerequisites
- Download the CLI to the current directory as
contrast. - Install Nix with
nix-commandandflakesenabled. - Install the GitHub CLI and
jq, and log in withgh auth login. - On macOS, configure an
x86_64-linuxremote builder for building the Linux artifacts.
Contrast verifies reproducibility weekly by building the node installer images from source on independent Ubuntu 22.04 and 24.04 hosts with the reproducibility workflow. If you also build on Ubuntu 23.10 or later, run the following to let the Nix build sandbox create user namespaces until the next reboot:
sudo sysctl kernel.apparmor_restrict_unprivileged_userns=0
Differences in the Nix version, the build host's filesystem, or the configured binary caches might cause mismatches, so we recommend staying close to that setup. If an artifact still differs from the release, please open an issue.
How-to
The build takes a long time. The node installer images contain the Contrast VM images, and the CLI embeds their digests. This requires building the VM images, including the guest firmware and kernel, for every supported platform and their GPU variants from source.
Check out the release
contrast_release=$(gh release view --repo edgelesssys/contrast --json tagName -q .tagName)
git clone --depth 1 --branch "$contrast_release" https://github.com/edgelesssys/contrast contrast-src
cd contrast-src
echo -n "${contrast_release#v}" >| version.txt # the tag carries the next development version
Container images
Build the container images and record their digests. The CLI and the deployment files reference the images by these digests.
image() {
out=$(nix build --no-link --print-out-paths ".#legacyPackages.x86_64-linux.base.${2}")
echo "ghcr.io/edgelesssys/contrast/${1}:latest=ghcr.io/edgelesssys/contrast/${1}:${contrast_release}@$(jq -r '.manifests[0].digest' "${out}/index.json")"
}
{
image coordinator containers.coordinator
image initializer containers.initializer
image service-mesh-proxy containers.service-mesh-proxy
image node-installer-kata contrast.node-installer-image
image node-installer-kata-gpu contrast.node-installer-image.gpu
image debugshell containers.debugshell
} >| cli/cmd/assets/image-replacements.txt
CLI
Build the CLI and compare it with the published binary:
nix build .#base.contrast.cli-release
cmp result/bin/contrast ../contrast
cmp prints nothing if the binaries are identical.
nix build produces the CLI for the platform you run it on, so run this step on macOS to check the macOS CLI.
Deployment files
Generate the Coordinator and runtime deployment files and check them against the release:
resourcegen() { nix run .#base.contrast.resourcegen -- --image-replacements cli/cmd/assets/image-replacements.txt "$@"; }
resourcegen --add-load-balancers coordinator >| coordinator.yml
for platform in $(gh release view "$contrast_release" --repo edgelesssys/contrast --json assets -q '.assets[].name | select(startswith("runtime-")) | ltrimstr("runtime-") | rtrimstr(".yml")'); do
resourcegen --namespace contrast-system --add-namespace-object --platform "$platform" runtime >| "runtime-${platform}.yml"
done
for file in coordinator.yml runtime-*.yml; do
gh release verify-asset "$contrast_release" "$file" --repo edgelesssys/contrast
done