mirror of
https://github.com/budtmo/docker-android.git
synced 2026-04-25 20:25:57 +03:00
[GH-ISSUE #88] Feature : Add architecture capabilities x86_64, armeabi-v7a, arm64-v8a #68
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/docker-android#68
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @thelittlefireman on GitHub (Jul 6, 2018).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/88
Please make sure that it is an issue / a feature request. If it is a question / help wanted, please visit our group chat. Thank you!
Operating System:
All
Docker Image:
all
Docker Version:
17.09
Docker-compose version (Only if you use it):
Docker Command to start docker-android:
Expected Behavior
Using x86, x86_64, armeabi-v7a, arm64-v8a
Actual Behavior
Using X86
Could it be possible to generate image for multiple Archi ? Actualy if i look right, we only use x86 image.
Could we generate containers for x86_64, armeabi-v7a, arm64-v8a
use this system images :
system-images;android-24;google_apis;arm64-v8a | 22 | Google APIs ARM 64 v8a System Image
system-images;android-24;google_apis;armeabi-v7a | 22 | Google APIs ARM EABI v7a System Image
system-images;android-24;google_apis;x86 | 22 | Google APIs Intel x86 Atom System Image
system-images;android-24;google_apis;x86_64
I'm pretty sure it will help for resolving issue for person who have black-screen issue or no hardware acceleration enable possibility (due to hardware limitation Synology OS, etc ) , etc #69 #75
Not huge work is needed, just this line https://github.com/butomo1989/docker-android/blob/4975ebcc47e020c2395e3a841e43cb1f28c451ed/release.sh#L59
Just need to overload the "processor" variable with "x86", "x86_64", arm ....
Actualy i'have not time to do this but maybe later
@budtmo commented on GitHub (Jul 6, 2018):
Hi @thelittlefireman ,
I think there is no benefit to support other arch for example arm image. It is because of the performance. personally I will not use the emulator with arm image that is really slow and need to wait for 10 minutes or even more until it is ready to use. But I am open if you have any other positive reasons why we need to do it. :)
@JoeSSS commented on GitHub (Jul 6, 2018):
Moreover, the last 3 API levels do not have ARM and others. So I believe that it is not supported from google as well.
@thelittlefireman commented on GitHub (Jul 10, 2018):
for exemple, for personal use I do not have hardware acceleration on my synology nas and I can not successfully run x86 version. And so as it run on my nas I dont matter to wait for 10 minutes :)
@aleksandrawy commented on GitHub (Jul 11, 2018):
Hi, I have a question about supporting x86 by Mac. When I create the emulator ex. simply from Android Studio and I choose the x86 ABI , I can run the created emulator without any problems (on macOS High Sierra). Can you explain me what is the difference between the android images that are available to get in Docker and those from ex. Android Studio?
@JoeSSS commented on GitHub (Jul 11, 2018):
The difference is the OS. On mac you can use HAXM which is supported by Mac's CPU. In its turn, the docker runs on linux which supports only kvm and kvm is not compatible with mac CPU.. So, there is no other ways around rather than create a Linux VM on your mac and run it there.
What we're doing in my company, is creating virtual device farm using this image and providing up to 16 devices running on remote Linux machine, so people are actually happy to do not run emulator on their Macs :)
@aleksandrawy commented on GitHub (Jul 11, 2018):
I want to use several emulator with different APIs to run the automated tests of application. I want to run them on Jenkins. Until now I run only one emulator and I wanted to dockerize it to run more than one emulator with own environments (appium server etc.). Jenkins is set on the Mac in my company and now I don't know how to run those automated tests on the several APIs. Should I create VM on each run or what? Do you have any ideas?
@v3g3t4x commented on GitHub (Jul 13, 2018):
@JoeSSS have you performance issue with your 16 devices ?
@JoeSSS commented on GitHub (Jul 13, 2018):
@v3g3t4x not that I know about. But you should have a powerful machine for that ;) For example my previous nodes could handle just 8 connections (it was 16 cores 16gb ram). Current ones are 48 cores and 150gb RAM, which is more than enough. So we even opened 4 executors more for app compile.
@JoeSSS commented on GitHub (Jul 13, 2018):
@aleksandrawy I would love to have your problem ;) But answering your question - you may want to use something like Anka (see here: https://www.youtube.com/watch?v=moTvToQZsI8 ) as using Linux docker images on macs without a Linux virtualisation level is just impossible.