7,540
edits
Changes
→Check the new machine
If the new VM was created with virtualbox driver, the VirtualBox graphical interface must be started with the same user, that the VM was created with, and the VirtualBox will discover the new VM automatically}}
===Check what was created=== ====Check the interfaces on the host==== ====Login to the new machine====<pre># docker-machine ssh manager ## . ## ## ## == ## ## ## ## ## === /"""""""""""""""""\___/ === ~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ / ===- ~~~ \______ o __/ \ \ __/ \____\_______/ _ _ ____ _ _| |__ ___ ___ | |_|___ \ __| | ___ ___| | _____ _ __| '_ \ / _ \ / _ \| __| __) / _` |/ _ \ / __| |/ / _ \ '__|| |_) | (_) | (_) | |_ / __/ (_| | (_) | (__| < __/ ||_.__/ \___/ \___/ \__|_____\__,_|\___/ \___|_|\_\___|_|Boot2Docker version 18.05.0-ce, build HEAD : b5d6989 - Thu May 10 16:35:28 UTC 2018Docker version 18.05.0-ce, build f150324</pre> Check the interfaces of the new VM: <pre>docker@manager:~$ ifconfigdocker0 inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0 ...eth0 inet addr:192.168.123.195 Bcast:192.168.123.255 Mask:255.255.255.0 ...eth1 inet addr:192.168.42.118 Bcast:192.168.42.255 Mask:255.255.255.0</pre>
