Arnaud:
> Dear Tails,
>
> first, let me quickly introduce myself, I'm Arnaud, part of the
> SilentKeys team. Please refer to this mail to remember about SilentKeys
> (it was quite a while ago):
> https://mailman.boum.org/pipermail/tails-project/2016-April/000488.html
>
> I've been trying to build a Tails image an didn't succeed yet.
I'll assume you are using our Vagrant setup with its apt-cacher-ng setup (since what you write further down indicates that).
> As for Tails, I checked out the tag '3.0-beta1', and that's what I'm
> trying to build at the moment.
Note that we pushed 3.0-beta2 just yesterday! :)
> So far, the build always fails sooner or later because of network
> failure, and most precisely name resolution failure. A typical log looks
> like that:
>
> Err http://time-based.snapshots.deb.tails.boum.org sid Release.gpg
> Could not resolve 'time-based.snapshots.deb.tails.boum.org'
It's probably not related to your problem, but: when building from a tag, Tails shouldn't use time-based.snapshots.deb.tails.boum.org but tagged.snapshots.deb.tails.boum.org. It's fixed when you build from the 3.0-beta2 tag.
> The failure doesn't always happen at the same point of the build. At
> first, I thought it was related to `apt`, but I also experienced in
> failure on a `curl` command (when downloading Tor Browser, in
> `config/chroot_local-hooks/10-tbb`). I don't have the log anymore, but
> it was also a name resolution failure.
Please retry with the 3.0-beta2 tag; I don't think it will fix your problem, but who knows?
Any way, we will need some .buildlog:s, or at least excerpts around the failures. Preferably several, of different types of failed network activity (failed .deb fetch, failed APT list fetch, failed wget, etc.). Please also check the journal (`sudo journalctl`) inside the builder guest around the time you get the build failure -- perhaps something else is going on?
One thing to note is that everything is completely cached after it has been downloaded once, excluding APT lists (from `apt update` which is run many times), so once you've reached a certain point of the build, the only thing that can fail due to network issues before that point is the APT list fetches. Is this what you experience?
Another thing to test is to clear your builder and start with a fresh one (and fresh cache):
rake vm:destroy
Cheers!
