When I checked my wireless connection, the ipv6 has no internet access while the ipv4 has internet access. I have tried searching on the internet regarding IP address issues but none of the given solutions worked for me. Also, the internet is all about dns servers could not be found ( i am starting to stress out about this issue.

1. Dockermachine Error Could Not Find Matching Ip For Mac Os
2. Dockermachine Error Could Not Find Matching Ip For Mac High Sierra
3. Dockermachine Error Could Not Find Matching Ip For Mac Catalina

If you are like me trying to run windows Docker containers in a hyper-v vm windows 10 guest on a windows 10 host, you might have come across above issue, we can fix this issue in two steps.

• Docker machine is not running! Run Oracle VM VirtualBox Manager as administrator and make sure “default” machine is “running”. Could not find matching IP.
• Docker-machine ip default. This proved a convenient way to setup env vars within shell scripts so I could do things like run psql from host and access the postgres container being used by my app. Disclaimer: I realize that docker.local is supposed to be a shortcut way to avoid using IP addresses with Docker for Mac, but for me it currently does.
• I'm not entirely sure how I managed to do this, but when making a new docker machine ( through docker-machine create), the boot2docker VM doesn't seem to be getting an IP address for the network interface that is associated with the displayed MAC address.
• The first step in spoofing your MAC address is to find the network interface device that you want to spoof. Go to StartControl PanelNetwork Connection. Then double click on the device that you want to spoof. Then click on the support tab and then click on details.

• First make sure you are running on most up to date windows 10, prerequisite for OS requirements is to have Windows 10 Anniversary Update.
• Second enable nested virtualization, why do we need to do that ?

In this case, Hyper-V has been configured to expose virtualization extensions to its guest VM. A guest VM can take advantage of this, and install its own hypervisor. It can then run its own guest VMs, more info visit msdn blog

So how to enable nested virtualization,

first turn off the vm, run below command on the host OS, I would say the root OS.

Enable networking for nested virtual machine, can be done in two ways Mac spoofing or NAT mode.

will go with Mac Spoofing, to enable MAC spoofing, run below command on host os.

Make sure the guest OS has enough memory to run MobyLinuxVm docker container to initialize, I would say at least 4 gigs.

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.

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.

Dockermachine Error Could Not Find Matching Ip For Mac Os

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

Dockermachine Error Could Not Find Matching Ip For Mac High Sierra

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:

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

5 Answers

Answers 1

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

Answers 2

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.

Answers 3

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.

Dockermachine Error Could Not Find Matching Ip For Mac Catalina

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.

Answers 4

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.

Answers 5

One day I woke up, and Docker didn't work with mentioned 'Could not find matching IP for MAC address ...'

What helped me it was to:

• uninstal Docker Toolbox
• uninstall VirtualBox
• remove folder C:Usersuser_name.docker
• remove folder C:Usersuser_name.VirtualBox
• install Docker Toolbox again