qubes-mirage-firewall/Dockerfile

# Pin the base image to a specific hash for maximum reproducibility.
# It will probably still work on newer images, though, unless an update
# changes some compiler optimisations (unlikely).
#FROM ocurrent/opam:fedora-32-ocaml-4.11
FROM ocurrent/opam@sha256:fce44a073ff874166b51c33a4e37782286d48dbba1b5aa43563a0dd35d15510f

# Pin last known-good version for reproducible builds.
# Remove this line (and the base image pin above) if you want to test with the
# latest versions.
RUN cd ~/opam-repository && git fetch origin master && git reset --hard 479a47921a489d11833e03cf949bfb612bd65e41 && opam update

RUN opam depext -i -y mirage
RUN mkdir /home/opam/qubes-mirage-firewall
ADD config.ml /home/opam/qubes-mirage-firewall/config.ml
WORKDIR /home/opam/qubes-mirage-firewall
RUN opam config exec -- mirage configure -t xen && make depend
CMD opam config exec -- mirage configure -t xen && \
    opam config exec -- make tar
Pin Docker base image to a specific hash Requested by Joanna Rutkowska. 2017-01-31 04:26:57 -05:00			`# Pin the base image to a specific hash for maximum reproducibility.`
Switch Docker base image from Alpine to Fedora There seems to be a problem with Xen events getting lost on Alpine. 2020-10-26 11:19:30 -04:00			`# It will probably still work on newer images, though, unless an update`
Pin Docker base image to a specific hash Requested by Joanna Rutkowska. 2017-01-31 04:26:57 -05:00			`# changes some compiler optimisations (unlikely).`
Update to mirage-qubes 0.9.1 for qrexec3 compatibility Also, switch to building with OCaml 4.11. 2020-12-03 11:11:56 -05:00			`#FROM ocurrent/opam:fedora-32-ocaml-4.11`
			`FROM ocurrent/opam@sha256:fce44a073ff874166b51c33a4e37782286d48dbba1b5aa43563a0dd35d15510f`
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
			`# Pin last known-good version for reproducible builds.`
Pin Docker base image to a specific hash Requested by Joanna Rutkowska. 2017-01-31 04:26:57 -05:00			`# Remove this line (and the base image pin above) if you want to test with the`
			`# latest versions.`
update to ethernet 3.0 API 2022-01-09 06:36:35 -05:00			`RUN cd ~/opam-repository && git fetch origin master && git reset --hard 479a47921a489d11833e03cf949bfb612bd65e41 && opam update`
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
BROKEN: Upgrade to Mirage 6 for solo5 PVH support For me, this mostly hangs at: ``` 2020-10-26 11:16:31 -00:00: INF [qubes.rexec] waiting for client... 2020-10-26 11:16:31 -00:00: INF [qubes.gui] waiting for client... 2020-10-26 11:16:31 -00:00: INF [qubes.db] connecting to server... ``` Sometimes it gets a bit further: ``` 2020-10-26 11:14:19 -00:00: INF [qubes.rexec] waiting for client... 2020-10-26 11:14:19 -00:00: INF [qubes.gui] waiting for client... 2020-10-26 11:14:19 -00:00: INF [qubes.db] connecting to server... 2020-10-26 11:14:19 -00:00: INF [qubes.db] connected 2020-10-26 11:14:19 -00:00: INF [qubes.rexec] client connected, using protocol version 2 2020-10-26 11:14:19 -00:00: INF [qubes.gui] client connected (screen size: 3840x2160 depth: 24 mem: 32401x) 2020-10-26 11:14:19 -00:00: INF [unikernel] GUI agent connected ``` 2020-08-19 09:09:01 -04:00			`RUN opam depext -i -y mirage`
Add option to build with Docker 2017-01-09 11:45:16 -05:00			`RUN mkdir /home/opam/qubes-mirage-firewall`
			`ADD config.ml /home/opam/qubes-mirage-firewall/config.ml`
			`WORKDIR /home/opam/qubes-mirage-firewall`
Update to new mirage-nat API 2017-03-05 11:31:04 -05:00			`RUN opam config exec -- mirage configure -t xen && make depend`
			`CMD opam config exec -- mirage configure -t xen && \`
Add option to build with Docker 2017-01-09 11:45:16 -05:00			`opam config exec -- make tar`