Howdy - having issues getting a build done following the docker instructions.
First, there’s something funky with the docker setup and trying to use the ‘v2.8-a14’ tag - output looks like:
$ docker run -v "/bigdrive/adam/e/src:/srv/src" -v "/bigdrive/adam/e/zips:/srv/zips" -v "/bigdrive/adam/e/logs:/srv/logs" -v "/bigdrive/adam/e/ccache:/srv/ccache" -e "BRANCH_NAME=v2.8-a14" -e "DEVICE_LIST=alphaplus" -e "REPO=https://gitlab.e.foundation/e/os/releases.git" registry.gitlab.e.foundation:5000/e/os/docker-lineage-cicd:community
Set cache size limit to 50.0 GB
/root/build.sh: line 46: DEVICE_LIST_V2.8-A14: invalid variable name
/root/build.sh: line 85: DEVICE_LIST_V2.8-A14: invalid variable name
So I tried v2.7-u, which at least started, but then it stopped and I presumed it required the blobs (though that was just a guess). After adding the blobs in and re-running the process, it failed due to some apparent syntactical issue with Android.bp files:
$ docker run -v "/bigdrive/adam/e/src:/srv/src" -v "/bigdrive/adam/e/zips:/srv/zips" -v "/bigdrive/adam/e/logs:/srv/logs" -v "/bigdrive/adam/e/ccache:/srv/ccache" -e "BRANCH_NAME=v2.7-u" -e "DEVICE_LIST=alphaplus" -e "REPO=https://gitlab.e.foundation/e/os/releases.git" registry.gitlab.e.foundation:5000/e/os/docker-lineage-cicd:community
Set cache size limit to 50.0 GB
>> [Fri Feb 28 23:31:11 UTC 2025] Branch: v2.7-u
>> [Fri Feb 28 23:31:11 UTC 2025] Devices: alphaplus,
>> [Fri Feb 28 23:31:58 UTC 2025] (Re)initializing branch repository
>> [Fri Feb 28 23:31:59 UTC 2025] Branch name v2.7-u is a tag on e/os/releases, prefixing with refs/tags/ for 'repo init'
>> [Fri Feb 28 23:31:59 UTC 2025] Running: yes | repo init -u "https://gitlab.e.foundation/e/os/releases.git" -b "refs/tags/v2.7-u"
>> [Fri Feb 28 23:31:59 UTC 2025] Copying '/srv/local_manifests/*.xml' to '.repo/local_manifests/'
>> [Fri Feb 28 23:32:00 UTC 2025] Syncing branch repository
>> [Fri Feb 28 23:34:32 UTC 2025] Setting "UNOFFICIAL" as release type
>> [Fri Feb 28 23:34:32 UTC 2025] Adding OTA URL overlay (for custom URL )
>> [Fri Feb 28 23:34:32 UTC 2025] Preparing build environment
>> [Fri Feb 28 23:34:32 UTC 2025] Starting build for alphaplus, v2.7-u branch
>> [Fri Feb 28 23:34:32 UTC 2025] ANDROID_JACK_VM_ARGS=-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G
>> [Fri Feb 28 23:34:32 UTC 2025] Switch to Python2
23:35:00 Build sandboxing disabled due to nsjail error.
Running product configuration...
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=14
LINEAGE_VERSION=2.7""-u-20250228-UNOFFICIAL-alphaplus
PRODUCT_INCLUDE_TAGS=com.android.mainline mainline_module_prebuilt_nightly
TARGET_PRODUCT=lineage_alphaplus
TARGET_BUILD_VARIANT=userdebug
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=generic
HOST_OS=linux
HOST_OS_EXTRA=Linux-6.12.16-gentoo-x86_64-x86_64-Ubuntu-20.04.6-LTS
HOST_CROSS_OS=windows
BUILD_ID=AP2A.240905.003
OUT_DIR=out
WITH_SU=false
PRODUCT_SOONG_NAMESPACES=device/lge/sm8150-common hardware/lge hardware/google/interfaces hardware/google/pixel hardware/lineage/interfaces/power-libperfmgr hardware/qcom-caf/common/libqti-perfd-client vendor/lge/sm8150-common device/lge/alphaplus vendor/lge/alphaplus hardware/qcom-caf/sm8150 vendor/qcom/opensource/commonsys/display vendor/qcom/opensource/commonsys-intf/display vendor/qcom/opensource/display vendor/qcom/opensource/data-ipa-cfg-mgr-legacy-um vendor/qcom/opensource/dataservices hardware/qcom-caf/wlan vendor/qcom/opensource/libfmjni
============================================
error: vendor/lge/sm8150-common/Android.bp:23:3: expected "}", found ":"
error: vendor/lge/alphaplus/Android.bp:24:3: expected "}", found ":"
23:35:02 fatal errors encountered
I’m not much of a fan of docker, so am going with attempting via a repo sync as per 07: Building an e ROM the Repo Sync way · Wiki · e / documentation / A Generic Guide on porting eOS · GitLab
Following those directions at least the v2.8-a14 tag was fine to use.
Are the above issues with the docker setup known problems? I’ve done a few searching in the forums to see if anyone’s had similar issues but nothing came up.