starred/docker-android
1
0
Fork 0
mirror of https://github.com/budtmo/docker-android.git synced 2026-04-25 20:25:57 +03:00
Code Issues 21 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #46] Outdated emulator in image with Android version 5.1.1 #36

New issue
Closed
opened 2026-03-01 15:39:33 +03:00 by kerem · 12 comments
kerem commented 2026-03-01 15:39:33 +03:00
Owner
Copy link

Originally created by @SvetA95 on GitHub (Nov 13, 2017).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/46

How can I resolve this?

Originally created by @SvetA95 on GitHub (Nov 13, 2017). Original GitHub issue: https://github.com/budtmo/docker-android/issues/46 How can I resolve this?
kerem closed this issue 2026-03-01 15:39:33 +03:00
kerem commented 2026-03-01 15:39:34 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Nov 13, 2017):

Hi @SvetA95 ,

Thank you for the issue. Could you more specific what do you mean with outdated emulator? and is it arm or x86 image?

<!-- gh-comment-id:343919623 --> @budtmo commented on GitHub (Nov 13, 2017): Hi @SvetA95 , Thank you for the issue. Could you more specific what do you mean with outdated emulator? and is it arm or x86 image?
kerem commented 2026-03-01 15:39:34 +03:00
Author
Owner
Copy link

@SvetA95 commented on GitHub (Nov 13, 2017):

Hi
I'm using your image to automate tests for Android. Today the test ran I got an error saying: Original error: Could not find a connected Android device.

After that I went inside the container and tried to start the emulator manually and got:
emulator: Listening for console connections on port: 5554
emulator: Serial number of this emulator (for ADB): emulator-5554
[140245043508992]:WARNING:./android/base/files/IniFile.cpp:158:Failed to process .ini file /root/.android/emu-update-last-check.ini for reading.
Your emulator is out of date, please update by launching Android Studio:

  • Start Android Studio
  • Select menu "Tools > Android > SDK Manager"
  • Click "SDK Tools" tab
  • Check "Android SDK Tools" checkbox
  • Click "OK"

[140245120202496]:WARNING:./android/base/files/IniFile.cpp:158:Failed to process .ini file /root/.android/emu-update-last-check.ini for reading.

<!-- gh-comment-id:343928037 --> @SvetA95 commented on GitHub (Nov 13, 2017): Hi I'm using your image to automate tests for Android. Today the test ran I got an error saying: Original error: Could not find a connected Android device. After that I went inside the container and tried to start the emulator manually and got: emulator: Listening for console connections on port: 5554 emulator: Serial number of this emulator (for ADB): emulator-5554 [140245043508992]:WARNING:./android/base/files/IniFile.cpp:158:Failed to process .ini file /root/.android/emu-update-last-check.ini for reading. Your emulator is out of date, please update by launching Android Studio: - Start Android Studio - Select menu "Tools > Android > SDK Manager" - Click "SDK Tools" tab - Check "Android SDK Tools" checkbox - Click "OK" [140245120202496]:WARNING:./android/base/files/IniFile.cpp:158:Failed to process .ini file /root/.android/emu-update-last-check.ini for reading.
kerem commented 2026-03-01 15:39:34 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Nov 13, 2017):

Thank you, I will check it later. is it x86 or arm image? @SvetA95

<!-- gh-comment-id:343935020 --> @budtmo commented on GitHub (Nov 13, 2017): Thank you, I will check it later. is it x86 or arm image? @SvetA95
kerem commented 2026-03-01 15:39:34 +03:00
Author
Owner
Copy link

@SvetA95 commented on GitHub (Nov 13, 2017):

Yes x86, butomo1989/docker-android-x86-5.1.1

<!-- gh-comment-id:343935346 --> @SvetA95 commented on GitHub (Nov 13, 2017): Yes x86, butomo1989/docker-android-x86-5.1.1
kerem commented 2026-03-01 15:39:34 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Nov 15, 2017):

Hi @SvetA95 ,

I cannot reproduce the error. I just checked it and it works fine with x86 image for version 5.1.1? my command was docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S6" --name android-container butomo1989/docker-android-x86-5.1.1. Could you tell me how you run the container?

<!-- gh-comment-id:344608600 --> @budtmo commented on GitHub (Nov 15, 2017): Hi @SvetA95 , I cannot reproduce the error. I just checked it and it works fine with x86 image for version 5.1.1? my command was `docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S6" --name android-container butomo1989/docker-android-x86-5.1.1`. Could you tell me how you run the container?
kerem commented 2026-03-01 15:39:34 +03:00
Author
Owner
Copy link

@SvetA95 commented on GitHub (Nov 15, 2017):

Hi @butomo1989

I'm using a docker-compose file with the following container configs:
android:
build:
context: docker/android
dockerfile: Dockerfile
privileged: true
volumes:
- ./tests:/usr/src/MRA_Android_App/tests
links:
- "db:database"
- "server"
ports:
- "4723:4723"
- "5554:5554"
- "5555:5555"
privileged: true
tty: true
environment:
- DEVICE=Nexus 7
- APPIUM=true
container_name: android_appium_tests

Dockerfile:
FROM butomo1989/docker-android-x86-5.1.1

WORKDIR /usr/src/MRA_Android_App

COPY supervisord.conf /usr/src/MRA_Android_App

install php

RUN apt-get update && apt-get install -y
php7.0
php7.0-bcmath
php7.0-cli
php7.0-common
php7.0-fpm
php7.0-gd
php7.0-gmp
php7.0-intl
php7.0-json
php7.0-mbstring
php7.0-mcrypt
php7.0-mysqlnd
php7.0-pdo
php7.0-xml
php7.0-curl
php7.0-zip
php7.0-dev
x11vnc
telnet
expect
supervisor

Install composer

COPY composer.json /usr/src/MRA_Android_App
COPY install_Composer.sh /usr/src/MRA_Android_App
RUN chmod +x /usr/src/MRA_Android_App/install_Composer.sh
RUN /usr/src/MRA_Android_App/install_Composer.sh
COPY emulator_Auth_Token.sh /usr/src/MRA_Android_App
RUN chmod +x /usr/src/MRA_Android_App/emulator_Auth_Token.sh

I am also able to start the container normally. The problem is when I go inside and try to start the emulator with command "emulator @device_name". Then I received the error mentioned in the previous post:
emulator: Listening for console connections on port: 5554
emulator: Serial number of this emulator (for ADB): emulator-5554
[140245043508992]:WARNING:./android/base/files/IniFile.cpp:158:Failed to process .ini file /root/.android/emu-update-last-check.ini for reading.
Your emulator is out of date, please update by launching Android Studio:

Start Android Studio
Select menu "Tools > Android > SDK Manager"
Click "SDK Tools" tab
Check "Android SDK Tools" checkbox
Click "OK"

[140245120202496]:WARNING:./android/base/files/IniFile.cpp:158:Failed to process .ini file /root/.android/emu-update-last-check.ini for reading.

<!-- gh-comment-id:344610065 --> @SvetA95 commented on GitHub (Nov 15, 2017): Hi @butomo1989 I'm using a docker-compose file with the following container configs: android: build: context: docker/android dockerfile: Dockerfile privileged: true volumes: - ./tests:/usr/src/MRA_Android_App/tests links: - "db:database" - "server" ports: - "4723:4723" - "5554:5554" - "5555:5555" privileged: true tty: true environment: - DEVICE=Nexus 7 - APPIUM=true container_name: android_appium_tests Dockerfile: FROM butomo1989/docker-android-x86-5.1.1 WORKDIR /usr/src/MRA_Android_App COPY supervisord.conf /usr/src/MRA_Android_App # install php RUN apt-get update && apt-get install -y \ php7.0 \ php7.0-bcmath \ php7.0-cli \ php7.0-common \ php7.0-fpm \ php7.0-gd \ php7.0-gmp \ php7.0-intl \ php7.0-json \ php7.0-mbstring \ php7.0-mcrypt \ php7.0-mysqlnd \ php7.0-pdo \ php7.0-xml \ php7.0-curl \ php7.0-zip \ php7.0-dev \ x11vnc \ telnet \ expect \ supervisor # Install composer COPY composer.json /usr/src/MRA_Android_App COPY install_Composer.sh /usr/src/MRA_Android_App RUN chmod +x /usr/src/MRA_Android_App/install_Composer.sh RUN /usr/src/MRA_Android_App/install_Composer.sh COPY emulator_Auth_Token.sh /usr/src/MRA_Android_App RUN chmod +x /usr/src/MRA_Android_App/emulator_Auth_Token.sh I am also able to start the container normally. The problem is when I go inside and try to start the emulator with command "emulator @device_name". Then I received the error mentioned in the previous post: emulator: Listening for console connections on port: 5554 emulator: Serial number of this emulator (for ADB): emulator-5554 [140245043508992]:WARNING:./android/base/files/IniFile.cpp:158:Failed to process .ini file /root/.android/emu-update-last-check.ini for reading. Your emulator is out of date, please update by launching Android Studio: Start Android Studio Select menu "Tools > Android > SDK Manager" Click "SDK Tools" tab Check "Android SDK Tools" checkbox Click "OK" [140245120202496]:WARNING:./android/base/files/IniFile.cpp:158:Failed to process .ini file /root/.android/emu-update-last-check.ini for reading.
kerem commented 2026-03-01 15:39:34 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Nov 15, 2017):

Hi @SvetA95 ,

It looks like you extend the existing docker image that I provide. maybe we can discuss in https://gitter.im/butomo1989/docker-android so I can help you and I can close this issue. :)

<!-- gh-comment-id:344614251 --> @budtmo commented on GitHub (Nov 15, 2017): Hi @SvetA95 , It looks like you extend the existing docker image that I provide. maybe we can discuss in https://gitter.im/butomo1989/docker-android so I can help you and I can close this issue. :)
kerem commented 2026-03-01 15:39:35 +03:00
Author
Owner
Copy link

@SvetA95 commented on GitHub (Nov 15, 2017):

Sure, but the fact that I have extended the image shouldn't matter right? The emulator comes from your docker image and me installing php inside the container along side it, shouldn't have anything to do with the error I'm getting

<!-- gh-comment-id:344615067 --> @SvetA95 commented on GitHub (Nov 15, 2017): Sure, but the fact that I have extended the image shouldn't matter right? The emulator comes from your docker image and me installing php inside the container along side it, shouldn't have anything to do with the error I'm getting
kerem commented 2026-03-01 15:39:35 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Nov 15, 2017):

hm.. Could you run the original docker image that I provide? does it work in your machine? if yes, I assume there is misconfiguration in the Dockerfile where you extend the functionalities from the original image. if not, please provide the logs.

<!-- gh-comment-id:344617129 --> @budtmo commented on GitHub (Nov 15, 2017): hm.. Could you run the original docker image that I provide? does it work in your machine? if yes, I assume there is misconfiguration in the Dockerfile where you extend the functionalities from the original image. if not, please provide the logs.
kerem commented 2026-03-01 15:39:35 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Nov 15, 2017):

the logs could be found in /var/log/supervisor/ inside container @SvetA95

<!-- gh-comment-id:344617670 --> @budtmo commented on GitHub (Nov 15, 2017): the logs could be found in /var/log/supervisor/ inside container @SvetA95
kerem commented 2026-03-01 15:39:35 +03:00
Author
Owner
Copy link

@SvetA95 commented on GitHub (Nov 15, 2017):

It worked in the base image, thanks. I'll try and figure out what's wrong with my setup. Closing the issue,

<!-- gh-comment-id:344621983 --> @SvetA95 commented on GitHub (Nov 15, 2017): It worked in the base image, thanks. I'll try and figure out what's wrong with my setup. Closing the issue,
kerem commented 2026-03-01 15:39:35 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Nov 15, 2017):

Let me know if you need any help. we can discuss it through bitter @SvetA95

<!-- gh-comment-id:344624247 --> @budtmo commented on GitHub (Nov 15, 2017): Let me know if you need any help. we can discuss it through bitter @SvetA95
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v3.3.0-p0
v3.2.2-p0
v3.2.0-p0
v3.1.1-p0
v3.1.0-p0
v3.0.2-p2
v3.0.2-p1
v3.0.2-p0
v3.0.1-p1
v3.0.1-p0
v2.19.0-p2
v2.19.0-p1
v2.19.0-p0
v2.18.0-p0
v2.16.2-p0
v2.15.0-p1
v2.15.0-p0
v2.11.4-p0
v2.11.2-p0
v2.11.1-p0
v2.5.4-p1
v2.5.4-p0
v2.5.1-p0
v2.5.0-p0
v2.4.1-p0
v2.3.0-p1
v2.3.0-p0
v2.2.2-p0
v2.1.3-p1
v2.1.3-p0
v2.0.1-p1
v2.0.0-p6
v2.0-p5
v2.0-p4
v2.0-p3
v2.0-p2
v2.0-p1
v1.10-p7
v1.10-p6
v1.10-p5
v1.10-p4
v1.10-p3
v1.10-p2
v1.10-p1
v1.9-p8
v1.9-p7
v1.9-p6
v1.9-p5
1.9-p4
1.9-p3
1.9-p2
1.9-p1
1.9-p0
1.8-p16
1.8-p15
1.8-p14
1.8-p13
1.8-p12
1.8-p11
1.8-p10
1.8-p9
1.8-p8
1.8-p7
1.8-p6
1.8-p5
1.8-p4
1.8-p3
1.8-p2
1.8-p1
1.8-p0
1.7-p1
1.7-p0
1.6-p8
1.6-p7
1.6-p6
1.6-p5
1.6-p4
1.6-p3
1.6-p2
1.6-p1
1.6-p0
1.5-p6
1.5-p5
1.5-p4
1.5-p3
1.5-p2
1.5-p1
1.5-p0
1.4-p1
1.4-p0
1.3-p5
1.3-p4
1.3-p3
1.3-p2
1.3-p1
1.3-p0
1.2
1.1-p1
1.1
1.0
0.9-p5
0.9-p4
0.9-p3
0.9-p2
0.9-p1
0.9
0.8
0.7
0.6
0.5
0.4
0.3
0.2
0.1
Labels
Clear labels   
bug

   
depends_on_docker

   
enhancement

   
help wanted

   
nice to have

   
waiting for response
No labels
bug
depends_on_docker
enhancement
help wanted
nice to have
waiting for response
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/docker-android#36
No description provided.