tracer0tong / android-emulator

Yet another Docker container with Android SDK and Android emulator
Apache License 2.0
246 stars 95 forks source link

SSH permission denied, VNC denied #20

Closed larsschwarz closed 7 years ago

larsschwarz commented 7 years ago

Running Docker on Windows 10, started with

$ docker run -d -P --name android tracer0tong/android-emulator

docker ps shows the container and available ports just fine.

$ docker ps
CONTAINER ID        IMAGE                          COMMAND             CREATED             STATUS              PORTS                                                                                                                       NAMES
a494f19f07a4        tracer0tong/android-emulator   "/entrypoint.sh"    32 minutes ago      Up 32 minutes       0.0.0.0:32772->22/tcp, 0.0.0.0:32771->5037/tcp, 0.0.0.0:32770->5554/tcp, 0.0.0.0:32769->5555/tcp, 0.0.0.0:32768->5900/tcp   android

When I try SSHing into it using user root it gives me "connection refused".

$ ssh root@0.0.0.0 -p 32722
ssh: connect to host 0.0.0.0 port 32722: Connection refused

Trying to connect via VNC (using RealVNC client and port 5900) it gives me "denied by remote host".

larsschwarz commented 7 years ago

Ok, seems the SSH issue can be solved by not using 0.0.0.0 but the Docker IP instead.

tracer0tong commented 7 years ago

You are right. There is a difference between Windows and Linux environments, Windows currently will run container in Oracle Virtual Box, that's why you should use another IP address.

Yury Leonychev

On 16 Oct 2016, at 06:17, Lars Schwarz notifications@github.com wrote:

Ok, seems the SSH issue can be solved by not using 0.0.0.0 but the Docker IP instead.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

larsschwarz commented 7 years ago

Thanks, still can't connect to the VNC server though, I see the process running, but when trying to connect with a VNC client it's always refusing the connection. Might be a similar issue with Docker on Windows though and I'll close this "issue".