-
Notifications
You must be signed in to change notification settings - Fork 2k
This machine has been allocated an IP address, but Docker Machine could not reach it successfully #4100
Comments
Anyone? Is this expected behavior? |
I'm having the same issue. Environment: macOS 10.12.5 Can't seem to find any solution to this error. |
I am having the same issue! |
I have the same issue on Ubuntu Desktop 16.04 today |
Just tried this today after not using docker for a while, brand new install, doesn't work. Tried removing the host-only interface from vbox, deleted my ~/.docker, no luck. |
Hi, For me, removing Virtual Box 5.1 and installing Virtual Box 5.0 work CentOS Linux release 7.3.1611 (Core) |
For me the problem is in VirtualBox 5.1
My environment: |
Same issue - I have docker running hosts on a different subnet that work just fine. Just docker-machine that is the issue. No routing set up to get to the 192.168.x.x subnet when creating the host. root@ubuntu:~# docker-machine version Tried host-only mode and get the exact same indications root@ubuntu: This machine has been allocated an IP address, but Docker Machine could not SSH for the machine should still work, but connecting to exposed ports, such as You may need to add the route manually, or use another related workaround. This could be due to a VPN, proxy, or host file configuration issue. You also might want to clear any VirtualBox host only interfaces you are not using. |
Hi all, removing Virtual Box 5.1 and installing Virtual Box 5.0 worked for me |
I ran into this problem as well, but fortunately VirtualBox recently released a new version 5.1.30 which made the issue go away for me. So seems to have been a problem in VirtualBox 5.1 up until this version. |
Updating VirtualBox fixed the errors for me. Thanks @baldervanx ! |
same issue with version 5.2.2 r119230 |
I had the same problem today with a new VM (VirtualBox 5.2.8 r121009). docker-machine ls would error out with a "timeout" and problems similar to the ones stated above. Then I remembered that I had connected to my work VPN. Shutdown the VPN connection and the problem went away! :-) docker-machine version 0.14.0, build 89b8332 |
same issue with:
|
Thanks @gautamsatpathy , I was having similar problem then came across your post. Somehow vpn messes it up. |
Same problem for me on Linux Mint 19 (based on Ubuntu 18.04) Docker version 18.06.1-ce, build e68fc7a Bringing the interface down and back up as suggested by ecylmz fixed it for me. |
same problem for
for Ubuntu 16.04.5 LTS |
same problem in the past when it happened I got it working again by deleting the machine and recreating it has just hit me again today and nothing works:
I can't do anything, it just doesn't work |
rebooting my laptop and then recreating the machine fixed it |
I believe the issue is multiple VBox IF devices being created. I had two: |
I have a little project called Fluentdocker here on GitHub. I've got a bug report that made me run my old
docker-machine
unit test and I get errors back when creating a new docker machine.This is the error output:
"This machine has been allocated an IP address, but Docker Machine could not reach it successfully.
SSH for the machine should still work, but connecting to exposed ports, such as the Docker daemon port (usually :2376), may not work properly.
You may need to add the route manually, or use another related workaround.
This could be due to a VPN, proxy, or host file configuration issue.
You also might want to clear any VirtualBox host only interfaces you are not using."
Howerver the new machine works - but it is hard for me to determine when such an operation has gone well or not during the create phase.
Cheers,
Mario
The text was updated successfully, but these errors were encountered: