starred/docker-android

Fork 0

mirror of https://github.com/budtmo/docker-android.git synced 2026-04-25 20:25:57 +03:00

[GH-ISSUE #208] Launching emulator, complains 32 bits #151

New issue

Closed

opened 2026-03-01 15:40:57 +03:00 by kerem · 8 comments

kerem commented

2026-03-01 15:40:57 +03:00

Owner

Originally created by @DavidPerezIngeniero on GitHub (Nov 8, 2019).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/208

🐛 Bug Report

Operating System:
CentOS 7.2

Docker Image:
budtmo/docker-android-x86-8.1

Docker Version:
Docker version 19.03.2, build 6a30dfc

Docker-compose version (Only if you use it):
Not used

Docker Command to start docker-android:
docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S6" -e LANGUAGE=es -e COUNTRY=ES --name android budtmo/docker-android-x86-8.1

Expected Behavior

Being able to launch android emulator

Actual Behavior

When launching:
emulator

I receive this error:

WARNING: Cannot decide host bitness because $SHELL is not properly defined; 32 bits assumed.
ERROR: 32-bit Linux Android emulator binaries are DEPRECATED, to use them
you will have to do at least one of the following:

   - Use the '-force-32bit' option when invoking 'emulator'.
   - Set ANDROID_EMULATOR_FORCE_32BIT to 'true' in your environment.

   Either one will allow you to use the 32-bit binaries, but please be
   aware that these will disappear in a future Android SDK release.
   Consider moving to a 64-bit Linux system before that happens.

Setting SHELL variable to /bin/bash doesn't help.
Related problem:https://stackoverflow.com/questions/36482964/ubuntu-android-studio-error-running-emulator-cannot-decide-host-bitness-32-bit

Originally created by @DavidPerezIngeniero on GitHub (Nov 8, 2019). Original GitHub issue: https://github.com/budtmo/docker-android/issues/208 ## 🐛 Bug Report Operating System: CentOS 7.2 Docker Image: budtmo/docker-android-x86-8.1 Docker Version: Docker version 19.03.2, build 6a30dfc Docker-compose version (Only if you use it): Not used Docker Command to start docker-android: docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S6" -e LANGUAGE=es -e COUNTRY=ES --name android budtmo/docker-android-x86-8.1 ## Expected Behavior Being able to launch android emulator ## Actual Behavior When launching: emulator I receive this error: WARNING: Cannot decide host bitness because $SHELL is not properly defined; 32 bits assumed. ERROR: 32-bit Linux Android emulator binaries are DEPRECATED, to use them you will have to do at least one of the following: - Use the '-force-32bit' option when invoking 'emulator'. - Set ANDROID_EMULATOR_FORCE_32BIT to 'true' in your environment. Either one will allow you to use the 32-bit binaries, but please be aware that these will disappear in a future Android SDK release. Consider moving to a 64-bit Linux system before that happens. Setting SHELL variable to /bin/bash doesn't help. Related problem:https://stackoverflow.com/questions/36482964/ubuntu-android-studio-error-running-emulator-cannot-decide-host-bitness-32-bit

kerem closed this issue

2026-03-01 15:40:57 +03:00

kerem commented

2026-03-01 15:40:58 +03:00

Author

Owner

@DavidPerezIngeniero commented on GitHub (Nov 8, 2019):

Another problem:

# emulator -force-32bit @samsung_galaxy_s6_8.1
sh: 1: file: not found
sh: 1: file: not found
WARNING: Cannot decide host bitness because $SHELL is not properly defined; 32 bits assumed.
PANIC: Missing emulator engine program for 'x86' CPU.

@DavidPerezIngeniero commented on GitHub (Nov 8, 2019): Another problem: ``` # emulator -force-32bit @samsung_galaxy_s6_8.1 sh: 1: file: not found sh: 1: file: not found WARNING: Cannot decide host bitness because $SHELL is not properly defined; 32 bits assumed. PANIC: Missing emulator engine program for 'x86' CPU. ```

kerem commented

2026-03-01 15:40:58 +03:00

Author

Owner

@DavidPerezIngeniero commented on GitHub (Nov 11, 2019):

Now testing with the android budtmo/docker-android-x86-9.0 image:

emulator: ERROR: x86 emulation currently requires hardware acceleration!
Please ensure KVM is properly installed and usable.
CPU acceleration status: KVM requires a CPU that supports vmx or svm
More info on configuring VM acceleration on Linux:
https://developer.android.com/studio/run/emulator-acceleration#vm-linux
General information on acceleration: https://developer.android.com/studio/run/emulator-acceleration.```

@DavidPerezIngeniero commented on GitHub (Nov 11, 2019): Now testing with the `android budtmo/docker-android-x86-9.0` image: ```# /root/emulator/emulator @samsung_galaxy_s6_9.0 emulator: ERROR: x86 emulation currently requires hardware acceleration! Please ensure KVM is properly installed and usable. CPU acceleration status: KVM requires a CPU that supports vmx or svm More info on configuring VM acceleration on Linux: https://developer.android.com/studio/run/emulator-acceleration#vm-linux General information on acceleration: https://developer.android.com/studio/run/emulator-acceleration.```

kerem commented

2026-03-01 15:40:58 +03:00

Author

Owner

@DavidPerezIngeniero commented on GitHub (Nov 11, 2019):

Possible workaround

@DavidPerezIngeniero commented on GitHub (Nov 11, 2019): [Possible workaround](https://github.com/ksoichiro/dockerfiles/issues/3)

kerem commented

2026-03-01 15:40:58 +03:00

Author

Owner

@DavidPerezIngeniero commented on GitHub (Nov 11, 2019):

The problem is maybe related to the fact that my Linux host is a virtual machine, by using vmware.

@DavidPerezIngeniero commented on GitHub (Nov 11, 2019): The problem is maybe related to the fact that my Linux host is a virtual machine, by using `vmware`.

kerem commented

2026-03-01 15:40:58 +03:00

Author

Owner

@DavidPerezIngeniero commented on GitHub (Nov 12, 2019):

Solved by installing in my Linux host the CPU HAXM instruction emulation.

@DavidPerezIngeniero commented on GitHub (Nov 12, 2019): Solved by installing in my Linux host the CPU HAXM instruction emulation.

kerem commented

2026-03-01 15:40:58 +03:00

Author

Owner

@gMan1990 commented on GitHub (Apr 26, 2020):

Solved by installing in my Linux host the CPU HAXM instruction emulation.

how ?

@gMan1990 commented on GitHub (Apr 26, 2020): > Solved by installing in my Linux host the CPU HAXM instruction emulation. how ?

kerem commented

2026-03-01 15:40:58 +03:00

Author

Owner

@sandikodev commented on GitHub (Feb 23, 2021):

Solved by installing in my Linux host the CPU HAXM instruction emulation.

how ?

here's for documentation
https://developer.android.com/studio/run/emulator-acceleration

@sandikodev commented on GitHub (Feb 23, 2021): > > Solved by installing in my Linux host the CPU HAXM instruction emulation. > > how ? here's for documentation `https://developer.android.com/studio/run/emulator-acceleration`

kerem commented

2026-03-01 15:40:58 +03:00

Author

Owner

@Kalela commented on GitHub (Aug 22, 2022):

Do I install HAXM into the docker image? For me, It opens the emulator when I use the provided docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S6" --name android-container budtmo/docker-android-x86-8.1 command. But I can't restart the emulator after rooting.

@Kalela commented on GitHub (Aug 22, 2022): Do I install HAXM into the docker image? For me, It opens the emulator when I use the provided ` docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S6" --name android-container budtmo/docker-android-x86-8.1 ` command. But I can't restart the emulator after rooting. ![image](https://user-images.githubusercontent.com/33759757/185997420-fa44b820-1ddc-4adc-a4f2-ec94606104bd.png)