-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSH connection time-out #22
Comments
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: |
Thank, found a temp solution with docker exec -ti containername sh |
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 I reinstalled docker and the image, but can't get it to work. Without the login, it's pretty useless. |
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: |
I followed the directions mentioned in the examples for OSC from @frosit and that seems to work fine now. Will continue to set up the M2 environment by importing from my Byte development server.
… On 24 Nov 2018, at 19:00, Rick van de Loo ***@***.***> wrote:
Hi @acjvenis <https://github.com/acjvenis>, perhaps this article is relevant to your situation https://docs.docker.com/docker-for-mac/networking/#known-limitations-use-cases-and-workarounds <https://docs.docker.com/docker-for-mac/networking/#known-limitations-use-cases-and-workarounds>. If you run the container like this for example:
docker run -p 1122:22 docker.hypernode.com/byteinternet/hypernode-docker:latest
perhaps then you will be able to SSH into the container via your local host like: ssh ***@***.*** -p 1122
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AVx4FodsmWdIDzzOxaunwVpFft785iEcks5uyYlbgaJpZM4YnA6r>.
|
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
The text was updated successfully, but these errors were encountered: