Switch to Ubuntu 18.04 for gitian building

laanwj commented at 7:35 pm on February 22, 2018: member

For 0.17 we should aim to use Ubuntu 18.04 for building. This will be the new LTS release of Ubuntu. We skipped 16.04 because of problems with the windows binary (#8732) but this was solved in 16.10, so ruling out new issues, the way should be clear.

This means finally building with a new C++ compiler, binutils, etc. Also this will solve a known security issue with the NSIS windows installer.

laanwj added the label Build system on Feb 22, 2018

laanwj added this to the milestone 0.17.0 on Feb 22, 2018

MarcoFalke commented at 7:46 pm on February 22, 2018: member

This means the travis configuration no longer mimics the gitian build configuration. I don’t think this leads to problems, since the travis configuration is the more ancient one.

laanwj commented at 8:46 pm on February 22, 2018: member

Right - upgrading the test infrastructure to the same version would be nice, though indeed not necessary as long as we’ll want to keep supporting building on 14.04.

ghost commented at 3:27 am on February 23, 2018: none

So it will be from Trusty to Bionic right?

laanwj commented at 10:33 am on February 23, 2018: member

So it will be from Trusty to Bionic right?

Correct. From Tahr to Beaver, jumping over the Xerus.

cdecker commented at 6:08 pm on March 9, 2018: contributor

We had the same issue with travis on another project and decided to bite the bullet and build in docker images that shipped with all the dependencies. Since we already use sudo: required it shouldn’t make CI testing much slower, but it feels a bit like operating through a keyhole to pass in the environment to the containers.

Sjors commented at 8:44 pm on March 15, 2018: member

Concept ACK

laanwj commented at 11:38 am on April 11, 2018: member

According to https://itsfoss.com/ubuntu-18-04-release-features/, release will be

5th April: Final beta release 19th April: Final Freeze 26th April: Stable Ubuntu 18.04 LTS release

luke-jr commented at 12:01 pm on April 11, 2018: member

vmbuilder will likely have difficulty, since it can’t handle the latest Debian stable. :/

TheCharlatan commented at 12:51 pm on April 16, 2018: member

@cdecker , the project you mentioned is similar to bitcoin? I am looking for a docker image that can handle new build utils, so I do not have to rely on whatever distro Travis is currently supporting. The Travis Xenial builds are still not officially supported. When I run them on my fork, I have to constantly restart them, since they stall on startup.

cdecker commented at 11:40 am on April 18, 2018: contributor

@TheCharlatan yes, it’s the c-lightning implementation we are working on, feel free to take a look at our .travis.yml and our builder docker images (in contrib/).

Sjors commented at 5:35 pm on April 30, 2018: member

Would it make sense to also change the suggested host (virtual) machine from Debian 8 to Ubuntu 18.04? Fewer distros to deal with in documentation and given Ubuntu’s popularity, it might increase the number of potential gitian signers who already have it. The required changes seem non-trivial though.

laanwj commented at 10:48 am on May 1, 2018: member

@sjors In principle I only care that the ‘suggested host’ way of working is documented and maintained (by regularly testing whether it still works). So I’m ok with switching it to Ubuntu if that’s easier. I chose Debian back in the day because of the minimalism.

I think it’s a good discussion to have, however it’s completely orthogonal to the issue of what to use as the guest.

MarcoFalke commented at 6:28 pm on May 2, 2018: member

Ideally it should work on any host that comes with the dependencies. However, the whole vmbuilder, lxc or kvm, gitian-builder setup on top of the host image that is bumped every couple of months seems extremly fragile. Wasn’t there some effort to move to something more out-of-the-box like docker? I think @achow101 once mentioned something on IRC?

achow101 commented at 6:33 pm on May 2, 2018: member

I think @achow101 once mentioned something on IRC?

I was working on using docker and docker images for gitian as an alternative to lxc or kvm (so it wouldn’t use vmbuilder and instead use standard docker images) although I got sidetracked from doing that.

ken2812221 commented at 9:29 pm on May 4, 2018: contributor

If I select gcc-7 for gitian-build, it failed at check-symbol. Do this mean that I should choose an older version of gcc?

0test/test_bitcoin: symbol __divmoddi4 from unsupported version GCC_7.0.0
1test/test_bitcoin: symbol log2f from unsupported version GLIBC_2.27
2qt/bitcoin-qt: symbol __divmoddi4 from unsupported version GCC_7.0.0
3qt/bitcoin-qt: symbol log2f from unsupported version GLIBC_2.27

laanwj referenced this in commit 6c6a3001e5 on Jul 10, 2018

laanwj closed this on Jul 16, 2018

fanquake referenced this in commit 19d8ca5cc1 on Jul 16, 2018

codablock referenced this in commit f411823c9a on Aug 13, 2018

codablock referenced this in commit 5c5bea3d72 on Aug 13, 2018

UdjinM6 referenced this in commit c09f57bd78 on Aug 13, 2018

cisba referenced this in commit 6b2b789283 on Sep 9, 2018

alejandromgk referenced this in commit eae1493884 on Feb 20, 2019

alejandromgk referenced this in commit 7aea08a255 on Apr 3, 2019

CryptoCentric referenced this in commit b1e5fac728 on Apr 25, 2019

10xcryptodev referenced this in commit 0c8f3447e4 on May 16, 2020

10xcryptodev referenced this in commit ce99b584ea on May 16, 2020

10xcryptodev referenced this in commit 4a7c3c22a7 on May 17, 2020

gades referenced this in commit 96fb7f3b6b on Jun 24, 2021

CryptoCentric referenced this in commit 7c4387a1a6 on Jul 2, 2021

DrahtBot locked this on Sep 8, 2021

Switch to Ubuntu 18.04 for gitian building #12511