docker-lineage-cicd VS LineageOTA

That is a great idea. Googling this gave me a great docker lineage ubuntu build image here: https://github.com/jfloff/docker-lineageos (or alternatively for microg? https://hub.docker.com/r/lineageos4microg/docker-lineage-cicd ). It looks like some older images (6+years) are in dockerhub as well. I like the approach by João (first link above) and will give it a go on my Intel i7 machine. I have an old school rotating HDD with enough space for the 80GB+ that lineageos seems to need for building.

In the FAQ of the official website this docker image is linked.

You're right, it's specific to LineageOS for microG, and https://github.com/lineageos4microg/docker-lineage-cicd/issues is the right place to report issues about it.

It uses this docker microservice to do the job.

However, I cannot find instructions on how to do it on the LineageOS for MicroG Docker GitHub page (link: https://github.com/lineageos4microg/docker-lineage-cicd). There has even been a issue/feature request opened for it, but it was closed as "Completed" without any response (link: https://github.com/lineageos4microg/docker-lineage-cicd/issues/336).

AFAIK signature spoofing is only activated for privileged aka system apps.

January 15th

These are the patches that enable signature spoofing permissions https://github.com/lineageos4microg/docker-lineage-cicd/blob/master/src/signature_spoofing_patches/android_frameworks_base-S.patch https://github.com/lineageos4microg/docker-lineage-cicd/blob/master/src/signature_spoofing_patches/packages_modules_Permission-S.patch you can see exactly what you need to change in the source files according to this. Also add https://github.com/lineageos4microg/docker-lineage-cicd/blob/master/src/signature_spoofing_patches/frameworks_base_config.xml#L19-L25 to your device overlay properties. Clone https://github.com/lineageos4microg/android_vendor_partner_gms into vendor/partner_gms (or anywhere else really for that matter, you can just copypaste it into your device tree) and add -include ../../../vendor/partner_gms/products/gms.mk (or whatever directory you have this in) into your device.mk

I am trying to build LineageOS for MicroG for an unsupported device by following the last example for building for unsupported devices on the GitHub page for building LineageOS for MicroG using Docker (https://github.com/lineageos4microg/docker-lineage-cicd). However, when I run the docker command, everything goes fine until it crashes and I get the following error:

I'm building my own images now because of the very inconsistent rate of microg builds for my device. Currently I am manually updating my device because I can't seem to figure out the OTA docker image. I already have a bunch of web services running on nginx, so I don't know if the incompatibility lies there or not, since it recommends apache. But I have seen some mentions of people using nginx, so it must be possible.

There's a container for running the OTA updates, which if it works for you, then you'd be in good shape - https://github.com/julianxhokaxhiu/LineageOTA