mirror of
https://github.com/budtmo/docker-android.git
synced 2026-04-26 04:35:52 +03:00
[GH-ISSUE #105] Container shows unhealthy #74
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/docker-android#74
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 @efg770 on GitHub (Jul 31, 2018).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/105
Running the container on Fedora28 with Docker version 18.03.1-ce, build 9ee9f40 and all is OK (this Linux box is fully connected to the internet)
Docker save of that image and import it into my own premise and I can't use it anymore as the container is unhealthy
The linux VM on my own-premise is RHEL 7.3 and docker 17.06
The logs shows:
root@f2b62ce84d5d:/var/log/supervisor# cat supervisord.log
2018-07-31 04:28:27,766 CRIT Supervisor running as root (no user in config file)
2018-07-31 04:28:27,774 INFO supervisord started with pid 7
2018-07-31 04:28:28,777 INFO spawned: 'xvfb' with pid 10
2018-07-31 04:28:28,779 INFO spawned: 'port-forward' with pid 11
2018-07-31 04:28:28,783 INFO spawned: 'novnc' with pid 12
2018-07-31 04:28:28,785 INFO spawned: 'openbox' with pid 13
2018-07-31 04:28:28,786 INFO spawned: 'x11vnc' with pid 14
2018-07-31 04:28:28,791 INFO spawned: 'android-screen-mirror' with pid 15
2018-07-31 04:28:28,792 INFO spawned: 'docker-appium' with pid 16
2018-07-31 04:28:28,793 INFO spawned: 'auto-recording' with pid 17
2018-07-31 04:28:28,808 INFO success: android-screen-mirror entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-07-31 04:28:28,808 INFO exited: android-screen-mirror (exit status 0; expected)
2018-07-31 04:28:29,852 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-07-31 04:28:29,853 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-07-31 04:28:29,853 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-07-31 04:28:29,853 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-07-31 04:28:29,853 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-07-31 04:28:29,853 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-07-31 04:28:29,853 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-07-31 04:28:33,122 INFO exited: docker-appium (exit status 0; expected)
2018-07-31 04:28:34,818 INFO exited: auto-recording (exit status 0; expected)
root@f2b62ce84d5d:/var/log/supervisor# cat video-recording.stdout.log
Auto record:
Auto recording is disabled!
@budtmo commented on GitHub (Jul 31, 2018):
Hi @efg770 ,
what do you mean with "Docker save of that image and import it into my own premise"? could you give more detail info about it?
@efg770 commented on GitHub (Jul 31, 2018):
As my Local linux VM on the internal VLAN does not have any internet access, I have to save the the image using: docker save > butomo1989/docker-android-x86-8.1 new-image.tar and then to copy it to the local VM and load it with: docker load --input new-image.tar
Now, once I have the image on my local VM, I just have to run it with your docker run command and get the unealthy state
@budtmo commented on GitHub (Jul 31, 2018):
please check if your linux VM support Virtualization then. @efg770
@budtmo commented on GitHub (Jul 31, 2018):
I will close this issue because it should work if your WM support virtualization. Please feel free to reopen it if there is a bug
@efg770 commented on GitHub (Aug 1, 2018):
No Problems
I am able to run the VM and get into the VNC terminal how do I start the
Android Emulator?
On Tue, Jul 31, 2018 at 5:51 PM Budi Utomo notifications@github.com wrote:
@efg770 commented on GitHub (Aug 1, 2018):
[image: image.png]
On Wed, Aug 1, 2018 at 12:50 PM Elad Fenigstein efg770@gmail.com wrote: