Updates gitian-build.sh script for the docker virtualization method recently added to gitian-builder.
Second commit depends on https://github.com/devrandom/gitian-builder/pull/185
Updates gitian-build.sh script for the docker virtualization method recently added to gitian-builder.
Second commit depends on https://github.com/devrandom/gitian-builder/pull/185
Concept ACK, thanks for working on this.
255 | @@ -238,6 +256,10 @@ then 256 | then 257 | sudo apt-get install lxc 258 | bin/make-base-vm --suite trusty --arch amd64 --lxc 259 | + elif [[ -n "$USE_DOCKER" ]] 260 | + then 261 | + sudo apt-get install docker-ce 262 | + bin/make-base-vm --suite trusty --arch amd64 --docker --docker-image-digest b8855dc848e2622653ab557d1ce2f4c34218a9380cceaa51ced85c5f3c8eb201
Are you sure that this digest will stay the same? They update the image very often. https://hub.docker.com/r/library/ubuntu/tags/
Edit: That make sure that docker always pull the same image base.
Is there any way to verify this hash?
I tried to build the image from scratch using https://github.com/tianon/docker-brew-ubuntu-core/blob/master/update.sh but it would give a different hash each run...
@achow101 Is this hash even supposed to be deterministic or does it just serve the purpose of an unique identifier?
I'm not sure.. I think it may just serve as a unique identifier.
In that case I'd prefer the second commit to be dropped. I believe for our purposes it suffices to use the "ubuntu:bionic" as a unique identifier.
utACK 86967b2e35d500bb4a5053c44aed809775a3e04e
Tested ACK 4b5b2c9c398237645450e25fe7188a3e0422e94a
I dropped the second commit that used gitian image hashes.
Do this actually work with latest version of gitian-builder? I always get a error message Error: No such container: gitian-target
@ken2812221 It works for me. Maybe you need to run it as root (with sudo) or set docker to run without root.