The following discussion from !956 should be addressed:
I'd like to create our own Android image to use, but the effort to produce it with pure Alpine is not worth it.
Instead I suggest we write down the exact steps to produce such an image, and make a Docker/Podman/LXC container which automatically executes those and produces a working image. We can then upload it somewhere for anbox-image to use.
— @PureTryOut
Edited
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
Activity
Sort or filter
Newest first
Oldest first
Show all activity
Show comments only
Show history only
Administratorchanged title from Create our own Anbox image to Create container for building own Anbox images·
Imported
changed title from Create our own Anbox image to Create container for building own Anbox images
I think we have sort of decided to use the newer Anbox images I have compiled locally for now.
The main difference to the prebuilts from Anbox is that they are all based on the latest Anbox source (so they should behave similarly). I have also rebased the Anbox patches on top of a new Android tag (was trivial, no conflicts), so they are built upon Android 7.1.2 with security patch level October 2019 (instead of 7.1.1 and January 2017).
It would still be useful to have some sort of container to build them. I have changed the issue title accordingly. I don't have much experience with container stuff myself.
I've settled for using a ubuntu/debian chroot. I've tried with Ubuntu 16.04 LTS Xenial Xerus so far (outdated OS, outdated build OS I guess, the AOSP setup page only listed 14.04 and older). The only dependencies needed on the host are debootstrap and arch-chroot. Both are present on Alpine.
sudo mount ~/anbox-image --bind-o ro /var/chroot/xenial/home/build/sourcesudo arch-chroot /var/chroot/xenial <<EOT2sudo mount /home/build/out --bind -o rw /home/build/source/out # building out of tree is brokensudo -u build /bin/bash <<EOTexport LC_ALL=en_US.UTF-8export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4096m"cd /home/build/source. build/envsetup.shlunch anbox_x86_64-userdebugmake -j8EOTEOT2