Repository navigation
SSH connection time-out #22
Description
Hi,
not able to use SSH when I follow the instructions. Any idea?
ssh -A app@172.17.0.2
PS C:\Users\sander> docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
793377232a82 docker.hypernode.com/byteinternet/hypernode-docker:latest "/sbin/my_init" 16 minutes ago Up 16 minutes 22/tcp, 80/tcp, 443/tcp, 1025/tcp, 3306/tcp, 6081/tcp, 8800/tcp, 8843/tcp, 8888/tcp hungry_haibt
PS C:\Users\sander> docker inspect -f '{{ .NetworkSettings.IPAddress }}' 793377232a82
172.17.0.2
Activity
vdloo commentedon Nov 18, 2018
Hi @SAPontwerp, we've heard of more people having trouble on Windows. I'm afraid I can't help you with that as this is probably is more of an issue relating to Docker on Windows (which is very different from Docker on Linux or Macs) than an issue relating to this specific Docker image. Have you tested your setup with other Docker images? Do you have the same networking issues with those? Perhaps try attaching to the container directly so you can poke around in the shell and look at the networking from inside the container and see what is going on:
docker exec -i -t <docker id> /bin/bash. See https://askubuntu.com/a/507009SvanZui commentedon Nov 18, 2018
Thank, found a temp solution with
docker exec -ti containername sh
acjvenis commentedon Nov 24, 2018
Actually, I am encountering the same problem, but then on a Mac. Cannot login to the Docker image, and get a time out on the ssh command.
0593462d7236 docker.hypernode.com/byteinternet/hypernode-docker:latest "/sbin/my_init" 24 minutes ago Up 24 minutes 22/tcp, 80/tcp, 443/tcp, 1025/tcp, 3306/tcp, 6081/tcp, 8800/tcp, 8843/tcp, 8888/tcp sleepy_almeida
docker inspect -f '{{ .NetworkSettings.IPAddress }}' 0593462d7236
172.17.0.2
I reinstalled docker and the image, but can't get it to work. Without the login, it's pretty useless.
vdloo commentedon Nov 24, 2018
Hi @acjvenis, perhaps this article is relevant to your situation https://docs.docker.com/docker-for-mac/networking/#known-limitations-use-cases-and-workarounds. If you run the container like this for example:
perhaps then you will be able to SSH into the container via your local host like:
ssh root@localhost -p 1122acjvenis commentedon Nov 24, 2018