Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content

Docker:community changes from 2023-10-27 broke my build setup

I have the same problems on two workstations.

Minimal Ubuntu 22.04 server install

DELL WORKSTATION Xeon 8cores, 32gB RAM

On both I could build in Sep/Okt then got problems on one workstation, not building anymore. Some days later I started the other workstation(at a different location) an I got the same problem. Both workstations are only used for building /e with docker and then turned off again.

Here is how I figured it has to do with the newer docker image:

$ docker  image ls
REPOSITORY                                                   TAG         IMAGE ID       CREATED        SIZE
registry.gitlab.e.foundation:5000/e/os/docker-lineage-cicd   community   70db1a246c88   2 months ago   1.92GB
registry.gitlab.e.foundation:5000/e/os/docker-lineage-cicd   <none>      9acfd3dbeed7   2 months ago   1.92GB
registry.gitlab.e.foundation/e/os/docker-lineage-cicd        community   29d835c75f03   4 months ago   1.92GB
registry.gitlab.e.foundation:5000/e/os/docker-lineage-cicd   <none>      29d835c75f03   4 months ago   1.92GB

$ docker inspect 70db1a246c88 | grep Created "Created": "2023-11-02T21:39:14.377717891Z", 
$ docker inspect 9acfd3dbeed7 | grep Created "Created": "2023-10-27T05:02:34.936152595Z", 
$ docker inspect 29d835c75f03 | grep Created "Created": "2023-08-31T04:37:40.101872176Z",
~/e/logs$ grep -r 'Failed build for' *
:>> [Tue Oct 31 16:49:45 UTC 2023] Failed build for jactivelte
:>> [Wed Nov  1 09:12:14 UTC 2023] Failed build for jfvelte
:>> [Thu Nov  2 07:07:45 UTC 2023] Failed build for jfvelte
:>> [Sat Jan  6 15:14:29 UTC 2024] Failed build for jfvelte
:>> [Sat Jan  6 18:03:53 UTC 2024] Failed build for jfvelte
:>> [Sat Jan  6 19:53:50 UTC 2024] Failed build for jfvelte
:>> [Wed Nov  1 23:43:28 UTC 2023] Failed build for jfvelte
:>> [Sat Jan  6 16:24:01 UTC 2024] Failed build for jfvelte
:>> [Tue Oct 31 20:31:12 UTC 2023] Failed build for jfvelte
:>> [Tue Oct 31 20:39:31 UTC 2023] Failed build for jfvelte
:>> [Tue Oct 31 20:43:58 UTC 2023] Failed build for jfvelte
:>> [Thu Nov  2 23:47:19 UTC 2023] Failed build for klte
:>> [Thu Nov  2 15:50:07 UTC 2023] Failed build for klte
:>> [Thu Nov  2 15:37:24 UTC 2023] Failed build for klte
:>> [Thu Nov  2 15:39:23 UTC 2023] Failed build for klte
:>> [Thu Nov  2 15:54:10 UTC 2023] Failed build for klte
:>> [Thu Nov  2 16:01:00 UTC 2023] Failed build for klte
:>> [Thu Nov  2 15:43:35 UTC 2023] Failed build for klte
:>> [Thu Nov  2 15:45:40 UTC 2023] Failed build for klte
:>> [Sat Jan  6 16:53:17 UTC 2024] Failed build for s5neolte
:>> [Sat Jan  6 17:25:05 UTC 2024] Failed build for s5neolte
:>> [Sat Jan  6 17:29:49 UTC 2024] Failed build for s5neolte
:>> [Thu Jan  4 09:23:42 UTC 2024] Failed build for s5neolte
:>> [Thu Jan  4 09:36:00 UTC 2024] Failed build for s5neolte
:>> [Thu Jan  4 09:47:01 UTC 2024] Failed build for s5neolte
:>> [Sat Jan  6 14:53:16 UTC 2024] Failed build for s5neolte
:>> [Thu Jan  4 09:39:48 UTC 2024] Failed build for s5neolte

Today I had time to try the 2nd WS again:

repo has been initialized in /srv/src/R
>> [Sat Jan 20 16:29:18 UTC 2024] Syncing branch repository
... A new version of repo (2.40) is available.
... You should upgrade soon:
cp /srv/src/R/.repo/repo/repo /usr/local/bin/repo
repo sync has finished successfully.

(I did copy the repo over, but that did not change anything and is a warning only anyway)

>> [Sat Jan 20 16:44:32 UTC 2024] Setting "MaKe::AQA-RCG@UNOFFICIAL" as release type
>> [Sat Jan 20 16:44:32 UTC 2024] Adding OTA URL overlay (for custom URL )
>> [Sat Jan 20 16:44:32 UTC 2024] Adding keys path (/srv/keys)
>> [Sat Jan 20 16:44:32 UTC 2024] Preparing build environment
>> [Sat Jan 20 16:44:32 UTC 2024] Starting build for a5y17lte, v1.19.1-r branch
>> [Sat Jan 20 16:44:32 UTC 2024] ANDROID_JACK_VM_ARGS= -Dfile.encoding=UTF-8  -XX:+TieredCompilation  -Xmx30G
>> [Sat Jan 20 16:44:32 UTC 2024] Switch to Python2
>> [Sat Jan 20 16:44:37 UTC 2024] Failed build for a5y17lte
>> [Sat Jan 20 16:44:37 UTC 2024] Finishing build for a5y17lte
>> [Sat Jan 20 16:44:37 UTC 2024] Cleaning source dir for device a5y17lte
>> [Sat Jan 20 16:44:38 UTC 2024] Switch back to Python3

On the forum @petefoth pointed out:

And one of the things that changed was to move to Python 3 instead of Python 2

Now, as per /e Docs I simply do a:

Get our docker image Tip:

Please run this step before each build, to be sure to get the last docker image.

$ sudo docker pull registry.gitlab.e.foundation:5000/e/os/docker-lineage-cicd:community

the docker container i then spin up shuld just work, right!?

But my otherwise unchanged build systems broke with this version:

$ docker inspect 70db1a246c88 | grep Created "Created": "2023-11-02T21:39:14.377717891Z"
Edited by Matt K/e