7,540
edits
Changes
→Interface list of the new VM
* '''virbr1''': That is the host-only virtual network that was created out-of-the-box. This one has no internet access.
<br>
====Interface list of the new VM====
You can log in to the newly created VM with the '''docker-machine ssh <machine_name>''' command
On the newly created docker ready VM, four interfaces were created.
* '''eth1''':192.168.42.118 - This connect to the dynamically created host-only virtual network. Just for VM-to-VM communication
* '''docker0''':172.17.0.1 - This VM is ment to host docker container, so the docker daemon was already installed and started on it. Form docker point of view, this VM is also a (docker) host, and therefore the docker daemon created the default virtual bridge, that the containers will be connected to unless it is specified implicitly otherwise during container creation.
Inspect the new VM with the '''docker-machine inspect''' command
<pre>
# docker-machine inspect manager
{
"ConfigVersion": 3,
"Driver": {
....
"CPU": 1,
"Network": "docker-network",
"PrivateNetwork": "docker-machines",
"ISO": "/root/.docker/machine/machines/manager/boot2docker.iso",
"...
},
"DriverName": "kvm",
"HostOptions": {
....
},
"SwarmOptions": {
"IsSwarm": false,
...
},
"AuthOptions": {
....
}
},
"Name": "manager"
}
</pre>
<br>