@aethernet looks like more changes are necessary
there is a prolematic PPA added that ends up bumping the glibc requirement higher than bionic.
https://github.com/balena-io/etcher/actions/runs/3593553166/jobs/6050703854#step:5:314

The following packages will be upgraded:
  libgcc1
1 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
Need to get 41.7 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu bionic/main amd64 libgcc1 amd64 1:11.1.0-1ubuntu1~18.04.1 [41.7 kB]

the ubuntu-toolchain-r ppa includes an updated libgcc1 system package (version 11) package that when installed causes all installed gcc/g++ to produce builds that are not compatible with the default libgcc1 in bionic and focal (version 8 and 10 respectively)

idk where that ppa is getting added in the buildsystem but it needs to be removed and is not necessay to build etcher

@aethernet its not the existance of libgcc1, that is a normal package, its the launchpad ppa that is in the buildsystem that causes the issue where it upgrades that system package

the ppa is still there after your latest commit
https://github.com/balena-io/etcher/actions/runs/3594586798/jobs/6053071258#step:5:319

mmh i see :(

Yeah i don't get where it comes from either, maybe it's a dep of something else, or part of the flow, still looking

The weird thing beeing it happens exactly between the installation of libgbm1 and lbgconf-2.4, ...

    - libgbm1
    - libgcc1
    - libgconf-2-4

The ppa is indeed ubuntu-toolchain-r, but the installation is only for libgcc1

it looks to be part of the official github runner image... https://github.com/actions/runner-images/blob/main/images/linux/scripts/installers/gcc.sh

thats not good, you could just remove the ppa programatically before any apt installs run, that would solve it

I'll look into this again tonight and double check that this is an actual issue. I know for a fact that if you install gcc-11 from that ppa it breaks backwards compatibiility with systems without the ppa, I will need to verify that upgrading libgcc1 is the reason or if it is libgcc-s1

why would it install it at that exact moment ? that's very suspicious to me.

btw i got confirmation that the build made on ubuntu 18.04 runs fine on unbuntu 20.04. (i won't have a 18.04 avail. tonight but i'll test that tomorrow myself)

I confirm it works on 18.04
I'm rebasing and will retest, but I believe we're good here.

@balena-ci I self-certify!