qubes-mirage-firewall/build-with-docker.sh

#!/bin/sh
set -eu
echo Building Docker image with dependencies..
docker build -t qubes-mirage-firewall .
echo Building Firewall...
docker run --rm -i -v `pwd`:/tmp/orb-build qubes-mirage-firewall
echo "SHA2 of build:   $(sha256sum ./dist/qubes-firewall.xen)"
echo "SHA2 last known: d9f7827e2f2c8150ac97a4d348a29f5ee0810a455dbab9233490fff97470f7b8"
echo "(hashes should match for released versions)"
Add option to build with Docker 2017-01-09 11:45:16 -05:00			`#!/bin/sh`
Fix opam-repository commit for reproducible builds Also, display the actual and expected SHA hashes after building. 2017-01-28 08:44:21 -05:00			`set -eu`
			`echo Building Docker image with dependencies..`
Add option to build with Docker 2017-01-09 11:45:16 -05:00			`docker build -t qubes-mirage-firewall .`
Fix opam-repository commit for reproducible builds Also, display the actual and expected SHA hashes after building. 2017-01-28 08:44:21 -05:00			`echo Building Firewall...`
Reproducible build systems: use in GitHub action the build-with-docker.sh Also upload the artifact to GitHub action, and in addition use the same setup (ubuntu 20.04 image) and build directories as done on builds.robur.coop. Also use `strip` on the resulting binary to reduce it's size (since the debug section aren't mapped into the running unikernel, there's nothing we get from them -- also they are preserved (as .debug file) and uploaded to https://builds.robur.coop if one needs them). This entails binary reproducibility between the different systems: - a developer using ./build-with-docker.sh - GitHub action (run on every PR) - builds.robur.coop with the ubuntu-20.04 worker 2022-11-13 06:22:59 -05:00			docker run --rm -i -v `pwd`:/tmp/orb-build qubes-mirage-firewall
update docker build for mirage 4.2 2022-08-09 08:16:16 -04:00			`echo "SHA2 of build: $(sha256sum ./dist/qubes-firewall.xen)"`
remove memreport to Xen to avoid Qubes trying to get back some memory from us 2023-05-26 04:27:29 -04:00			`echo "SHA2 last known: d9f7827e2f2c8150ac97a4d348a29f5ee0810a455dbab9233490fff97470f7b8"`
Note that Git versions might have different hashes 2019-01-19 05:32:27 -05:00			`echo "(hashes should match for released versions)"`