10/8/2021

Dockermachine Error Could Not Find Matching Ip For Mac

81

2021腾讯云限时秒杀,爆款1核2G云服务器298元/3年!(领取2860元代金券),
地址:https://cloud.tencent.com/act/cps/redirect?redirect=1062

2021阿里云最低价产品入口+领取代金券(老用户3折起),
入口地址:https://www.aliyun.com/minisite/goods

I got strange problem with docker-machine on windows 10. And I still cannot find solution.

It used to work before, but after some update of Windows 10 I began to get error 'Could not find matching IP for MAC address ...'. This error appears on any action with docker-machine.

Also removed default docker-machine on existing set up after the new installation failed by doing docker-machine rm default Also, one thing to notice that when I do a clean install, I can see that when I fire up the docker quickstart for the first time it starts everything from the scratch except one thing. The MAC filter combo box field configures the engine as: MAC Filter: Off - All DHCP requests are honored. (default) Accept - Only requests with MACs that match a predefined set of addresses are honored. Ignore - Only requests with MACs that do not match a predefined set of addresses are honored.

For example, with docker-machine ls:

I tried to reinstall dockertools with virtual box (with different network drivers). Tried to install latest version of virtual box. Remove and recreate docker virtual machine. Remove all vitrualbox host-only networks. It all doesn't help.

Here is what I get with docker-machine -D create -d virtualbox default:

docker-machine env default:

docker-machine regenerate-certs:

Could anybody point me in the right direction? What can cause such problem?

Thanks!

I've tried method suggested by VonC.

  1. Remove virtualbox and clean drivers and registry how suggested.
  2. Reboot PC.
  3. Install latest virtualbox (Version 5.0.18 r106667)
  4. Reboot PC.
  5. Set environment as suggested.

This is result.

C:UsersVadim>rem minimal path:

C:UsersVadim>set PATH=C:Windowssystem32;C:Windows;C:WindowsSystem32Wbem

C:UsersVadim>rem add Git to PATH

C:UsersVadim>rem set glatest=PortableGit-2.8.1-64-bit

C:UsersVadim>set PATH=C:Windowssystem32;C:Windows;C:WindowsSystem32Wbem; C:Program FilesGitbin;C:Program FilesGitusrbin;C:Program FilesGit

C:UsersVadim>set TERM=msys

C:UsersVadim>set GIT_HOME=C:Program FilesGit

C:UsersVadim>rem add VirtualBox to PATH

C:UsersVadim>set PATH=C:Windowssystem32;C:Windows;C:WindowsSystem32Wbem; C:Program FilesGitbin;C:Program FilesGitusrbin;C:Program FilesGit;C:Pr ogram FilesOracleVirtualBox

C:UsersVadim>rem add docker-machine to PATH

C:UsersVadim>set PATH=C:Windowssystem32;C:Windows;C:WindowsSystem32Wbem; C:Program FilesGitbin;C:Program FilesGitusrbin;C:Program FilesGit;C:Pr ogram FilesOracleVirtualBox;C:Program FilesDocker Toolbox

C:UsersVadim>set path Path=C:Windowssystem32;C:Windows;C:WindowsSystem32Wbem;C:Program FilesGi tbin;C:Program FilesGitusrbin;C:Program FilesGit;C:Program FilesOracle VirtualBox;C:Program FilesDocker Toolbox PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

C:UsersVadim>docker-machine create -d virtualbox test Running pre-create checks... Creating machine... (test) Copying C:UsersVadim.dockermachinecacheboot2docker.iso to C:Users Vadim.dockermachinemachinestestboot2docker.iso... (test) Creating VirtualBox VM... (test) Creating SSH key... (test) Starting the VM... (test) Check network to re-create if needed... (test) Windows might ask for the permission to create a network adapter. Sometim es, such confirmation window is minimized in the taskbar. (test) Found a new host-only adapter: 'VirtualBox Host-Only Ethernet Adapter #2'

(test) Windows might ask for the permission to configure a network adapter. Some times, such confirmation window is minimized in the taskbar. (test) Windows might ask for the permission to configure a dhcp server. Sometime s, such confirmation window is minimized in the taskbar. (test) Waiting for an IP... Waiting for machine to be running, this may take a few minutes... Detecting operating system of created instance... Waiting for SSH to be available... Detecting the provisioner... Provisioning with boot2docker... Copying certs to the local machine directory... Copying certs to the remote machine... Error creating machine: Error running provisioning: Could not find matching IP f or MAC address 080027d6b14d

I still get this error about IP and MAC.

Further investigation. As was suggested by VonC I've retried this with docker-machine 0.6.0. And I got other error:

As it's obviously trying to work with eth1 interface on virtual machine I've checked what's going on (all this time I could see vms created and worked in virtual box interface). This is what I see into guest VM:

Dockermachine error could not find matching ip for mac high sierra

As you can see eth1 interface doesn't have ip4 address specified. Can it be the cause of problem and how to fix it?

dockerdocker-machine

this questionedited Apr 23 '16 at 0:40 asked Apr 22 '16 at 2:53 Vadim 752 1 5 8 Do you have Hyper-v Microsoft feature active? – VonC Apr 22 '16 at 8:18 I don't, because I'm on Windows 10 Home. But it worked before (it worked last week). I also can create virtualbox vms myself and run them. Do I have a chance? – Vadim Apr 22 '16 at 12:23

4 Answers
4

Open virtual box, remove docker vm. Thet start quick-start again. I have same problem too on windows.



this answer answered Apr 22 '16 at 6:05 evtuhovdo 124 1 7 I tried this many times. With or without reboot, reinstalling vitrualbox, reinstalling docker, removing host only adapters. In every possible combinations. Nothing helps :( – Vadim Apr 22 '16 at 6:27

I had this same problem. I solved it by:

1) Remove the 'VirtualBox Host-Only Ethernet Adapter' using the VirtualBox Manager gui. (Preferences->Network->Host-only Networks) In fact there were 2 of these; I deleted both.

2) Delete the default VM (again, using the VirtualBox Manager gui)

3) re-run the start.sh script

Further notes: I'm using Windows 7 and cygwin64. The start.sh script has issues with finding the path to vboxmanage. While solving these errors, I ran the start.sh script multiple times, which probably accounts for the strange state that VBox found itself in.



this answeredited May 9 '16 at 10:55Lucas Barros 1,011 5 15 answered May 9 '16 at 10:21 Aaron Knauf 31 1 1. Done many times. 2. Also done many times. 3. Which start.sh? – Vadim May 9 '16 at 11:46 The start.sh script that I refer to is in C:Program FilesDocker Toolbox. It is the same script that is executed by the Docker Quickstart Terminal shortcut. Personally, I run it - and all docker/machine commands from a cygwin terminal, rather than using the shortcut. If you read it, you will see that it does a few extra steps than just the dm create that you are trying to do - e.g. rm -rf ~/.docker/machine/machines/'${VM}' – Aaron Knauf May 11 '16 at 10:07 I see from the output that you have posted that you get this message: Found a new host-only adapter: 'VirtualBox Host-Only Ethernet Adapter #2'. Does the adapter with that name have DHCP enabled in the Virtualbox preferences? – Aaron Knauf May 11 '16 at 10:36 Yes it had. I also tried to remove all adapters from virtual box, and let docker to create them. It didn't change anything. – Vadim May 12 '16 at 2:34 This seems to have resolved the issue for me. – Dennis W Feb 17 at 21:58

That error message comes from 'Determine host-only interface dynamically, stop assuming eth1' and PR 3112 fixing issue 3108

I would try to:

  • uninstall completely VirtualBox,
  • delete any vbox* file in C:Windowssystem32drivers,
  • delete any vbox* folders in HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservices
  • reinstall virtualbox 5.0.18 and its Oracle VM VirtualBox Extension Pack
  • use CMD only (no bash to avoid any side-effect)

Set your PATH by an senv.bat script which would include (change the path to your setup):

Than, in that new environment, with the latest docker-machine 0.7.0, create a new machine:

(use ssh from docker-machine, not ssh from a git bash)

Kevin Hooke mentions below in the comments (July 2016):

I had this same error on 1.11.2 on Windows 7 after downloading and installing the latest Toolbox. Error only started after updating Toolbox.

Even after deleting the default VM in VirtualBox would get the same error when it was recreated.

I noticed in the ticket mentioned in the answer above on GitHub that it mentions VirtualBox 5.0.14, so I just updated to 5.0.24. Started up the Quickstart prompt, it recreated the default vm, and now no issue.



this answeredited Jul 16 '16 at 4:34 answered Apr 22 '16 at 7:11 VonC 667k 215 1962 2085 Thanks for your answer. I've edited my question with results of your suggestion. It doesn't work. – Vadim Apr 22 '16 at 8:10 @Vadim Would this work with docker-machine 0.6.0? ( github.com/docker/machine/releases/tag/v0.6.0) – VonC Apr 22 '16 at 8:24 C:UsersVadim>docker-machine version docker-machine version 0.6.0, build e27fb87 C:UsersVadim>docker-machine create -d virtualbox test Running pre-create checks... Creating machine... (test) Copying C:UsersVadim.dockermachinecacheboot2docker.iso to C:Users Vadim.dockermachinemachinestestboot2docker.iso... (test) Creating VirtualBox VM... (test) Creating SSH key... (test) Starting the VM... (test) Check network to re-create if needed... (test) Waiting for an IP... Error creating machine: Error in driver during machine creation: Maximum number of retries (5) exceeded – Vadim Apr 22 '16 at 12:30 Now I have other error – Vadim Apr 22 '16 at 12:30 But I see this vm in VirtualBox interface, can show it, it's working! It's just cannot be managed by docker-machine. – Vadim Apr 22 '16 at 12:37 show more comments

If different IP (from previous run) is assigned on restart, docker-machine shows connectivity issues with the VM.
One approach that worked for me is to restart it in a way so that it gets same IP at restart.
E.g. if 192.168.99.102 (third in seq 100, 101, 102) was assigned at creation, then start any two other VMs before this docker machine, so that this one gets 102.

I am maintaining the commands, which had been handy in running docker in my initial days for reference:
Handy commands on docker-machine, docker and docker-compose for starters.



this answer answered Sep 28 '16 at 17:43 Sunil G. 1

Dockermachine Error Could Not Find Matching Ip For Mac Osx

Recommend:Docker on windows 7 error: 'docker machine not listening after creation'

Lab without connection to the internet. After it I perform following actions 1. I created a vm: 'docker-machine create -d virtualbox lab'. 2. Than i called: 'docker-machine start lab'. In responde i get: 'unable to verify the docker daemon