Sunday, 15 February 2015

jenkins - Android emulator in Docker -


I am trying to start an Android emulator inside the Docker Container, but I get an error:

< Pre> Route @ 686d602e6ffa: ~ / android-sdk-linux / tools #. / Memulator ERROR: 32-bit Linux Android Emulator Binaries have been removed, to use them you have to do at least one of the following: - 'Force-32bit' option when using 'emulator' - Set ANDROID_EMULATOR_FORCE_32BIT to 'right' in your environment, or anyone will allow you to use 32-bit binary, but please keep in mind that they will disappear in the future Android SDK release. Before going this, consider going to the 64-bit Linux system.

But inside the container is the OS ( uname -a )

Ubuntu SMP Tues 10 20:06:50 UTC 2015 X86_64 x86_64 x86_64 GNU / Linux

and manually imilotox 64-x86 works fine:

  android-sdk-linux / tools #. / Emulator64-x86 emulator: Error: You name the Android virtual device '-ded & lt; Name & gt; Had not given up with the option. Read -help-avd for more information. If you want to * actually * not * run an AVD, then '-Data & lt; File & gt; To specify a data partition image file (I hope you know what you are doing).  

I can make a symbolic link - but I think that this is not a good solution because there may be different architecture for simulation

besides This user must be started by Jenkins

UPDATED: as suggested by @ user2915097: root @ 686d602e6ffa: / # file / bin / bash / bin / bash: LSB executable for ELF 64-bit GNU / Linux 2.6.24, x86-64, version 1 (SYSV), dynamically linked (high on shared lbs) Itemprop = "text">

In the form of a FYI: I call it

Fodder went to the Docker based on Ubuntu: 16.04 and finally install it "file" apt-file

apparently looking at the AMUulator $ shell Uses file and if there is no "x86_64" in it, it seems that it is 32 bits.


No comments:

Post a Comment