[HOWTO] An unofficial / e / ROM built with Docker – in pictures

good work, thanks for the howto

Love it, thank you.
Worked fine in Debian too, package available I used for my first build (don’t do this on Ubuntu, search at Ubuntu itself):
And a screenshot from https://docs.docker.com/install/
about support in different Gnu-Linux distributions.

Thank you for this tutorial.

Im using this script on ubuntu to install docker in faster way https://get.docker.com/ just open terminal and type this comands :
curl -fsSL https://get.docker.com -o get-docker.sh
sh get-docker.sh


Hello, I tried to build the /e/ ROM by following the information in your documentation (https://doc.e.foundation/how-tos/build-e).

Unfortunately, I didn’t manage to run the docker image. I used this command line:

sudo docker run
-v “/srv/e/src:/srv/src:delegated”
-v “/srv/e/zips:/srv/zips:delegated”
-v “/srv/e/logs:/srv/logs:delegated”
-v “/srv/e/ccache:/srv/ccache:delegated”
-e “BRANCH_NAME=v1-nougat”
-e “DEVICE_LIST=kiwi”
-e “CUSTOM_PACKAGES=‘MuPDF GmsCore GsfProxy FakeStore com.google.android.maps.jar Mail BlissLauncher BlissIconPack MozillaNlpBackend OpenWeatherMapWeatherProvider AccountManager MagicEarth OpenCamera eDrive Weather Notes Tasks NominatimNlpBackend Light DroidGuard OpenKeychain Message Browser BrowserWebView Apps LibreOfficeViewer’”
-e “SIGNATURE_SPOOFING=restricted”
-e “OTA_URL=https://ota.ecloud.global/api”
-e “REPO=https://gitlab.e.foundation/e/os/android.git”

I have the following error:

[ 4% 2422/50023] target Java: org.cyanogenmod.platform.sdk (/srv/src/NOUGAT/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes)
FAILED: /bin/bash -c "(rm -f […] )
javac: file not found: /srv/src/NOUGAT/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/cyanogenmod/platform/Manifest.java
Usage: javac
use -help for a list of possible options
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target ‘ninja_wrapper’ failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory ‘/srv/src/NOUGAT’

make failed to build some targets (18:56 (mm:ss))

[Mon Oct 21 09:53:19 UTC 2019] Failed build for kiwi
[Mon Oct 21 09:53:19 UTC 2019] Finishing build for kiwi
[Mon Oct 21 09:53:19 UTC 2019] Cleaning source dir for device kiwi

Could you please help me fix this issue ?

Thanks in advance.


There were some complaints from users that the latest Docker build commands do not work.

To test this I tried out the same commands and it worked perfectly on the very first attempt!!
To be honest I expected a crash as I have a 6 year old PC which has some attitude issues.

All the same the build was successful and I share details of the commands I ran.

  • I downloaded the latest docker image.

    There was a recent change in the Docker image so first of all those of you who used to build or have tried to build the /e/OS ROM using Docker should delete the previous image

  • The command to delete Docker images are given here

    • Delete all images

      docker rmi $(docker images -q)

    • Show all images ( if you want to delete the image by its ID)

      docker image ls

    • Remove image by id ( assuming 75f08d5b848d is the image Id)

      docker rmi 75f08d5b848d

  • Now run the command to pull the latest Docker image as given here

  • This is how the image pull will appear on your Console

  • I created the folder structure - as described in step 3 here - for the Docker build in my home directory. The build and source code will require more than 100 GB space… i will check and update the exact space it takes on my HDD … it looks like this

  • The build command - step 4 - changes for me because of my local folder structure and looks like this

docker run \
-v "/home/manoj/e/src:/srv/src" \
-v "/home/manoj/e/zips:/srv/zips" \
-v "/home/manoj/e/logs:/srv/logs" \
-v "/home/manoj/e/ccache:/srv/ccache" \
-e "BRANCH_NAME=v1-pie" \
-e "DEVICE_LIST=a3xelte" \
-e "OTA_URL=" \
-e "REPO=https://gitlab.e.foundation/e/os/android.git" \

Note I change the following :

  • DEVICE_LIST = added the device code of the device I want to build for
  • OTA_URL = kept it blank as I do not provide any OTA builds
  • BRANCH_NAME = wanted it to point to the pie code

This is how the build looks once it starts running

At this point it looks like the PC has crashed or at least gone to sleep :slight_smile:
You can check what is happening by looking at the logs which will be available in the log folder you created above

  • What happens now depends on your internet speed . There is a lot of files to download. A minimum of 100 GB will be downloaded so it helps if you have a reasonably good download speed
  • Finally when all the files are downloaded the build starts . Now the screen will look like this

OS used : Ubuntu 20.04 LTS
RAM : 16 Gb
HDD : 1 Tb

1 Like

this is only working in ‘community’ image. On ‘latest’ image you have change to DEVICE only and remove OTA line

The ‘latest’ image is no longer to be used. The ‘community’ image is the one that is to be used for Docker.

Ah, OK, that’s why my tries yesterday where failing :frowning:

You can also cleanup Docker (no container running) with : docker system prune -a
Then check with docker system df -v

Test build for a3exlte on Ubuntu 18.04.4 LTS ok :slight_smile:

But builds still fail for Xiaomi devices (tested chiron, santoni, polaris).
Updated issue #1185

This is why Xiaomi devices will not work with Docker now. This ban has been in place for almost a year now. For Xiaomi devices you will have to extract the blobs and then run the builds. Never tried that on Docker but it works on the repo sync way.

I think the problem is the naming. Lineage uses this repo. You can see the build error: build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_suzuran". Stop. build/core/product_config.mk:249: *** Can not locate config makefile for product "cm_suzuran". Stop. build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_suzuran". Stop. The build system does not look for PRODUCT_NAME := full_suzuran. Don’t know why Lineage uses that naming.

Thank you. I should have known to look at the start of the logfile rather than the end :slight_smile:
I should be able to do some digging and find out what needs to change

you have 2 posts about the same issue. Pls compress to one, because It’s worst to answer.
And in a HowTo it’s not so good located.

by the way, I have answered on your other post

Problem with Xiaomi building is solved, commented & closed case #1185.

Currently forking Muppets GitLab repo as https://gitlab.com/smu44/proprietary_vendor_xiaomi/ for backup (couldn’t mirror, unfortunately).

All Xiaomi vendor sources are available at gitlab/the-muppets

That’s what I wrote in the issue’s comment :wink:
I made a backup just in case of DMCA, but many have already done the same :slight_smile:

Haven’t had a look on it. And yeah, I also have done a backup :blush:

So is this an unofficial build for a SUPPORTED device?

It would be easier to understand if you had listed all the pre-requistes.

Even better you could have updated the WIKI rather than linking to it.

Duplication simply leads to new users like me having to read more sources of documentation, which inevitably get out of sync.