after init and up commands give bad advice if settings are changed.

[SvenDowideit]

as an example

sven:~$ ./boot2docker --vm=test --dockerport=424 init
2014/05/16 15:55:36 Creating VM test...
2014/05/16 15:55:36 Apply interim patch to VM test (https://www.virtualbox.org/ticket/12748)
2014/05/16 15:55:36 Setting NIC #1 to use NAT network...
2014/05/16 15:55:36 Port forwarding [ssh] tcp://127.0.0.1:2022 --> :22
2014/05/16 15:55:36 Port forwarding [docker] tcp://127.0.0.1:424 --> :4243
2014/05/16 15:55:36 Setting NIC #2 to use host-only network "vboxnet0"...
2014/05/16 15:55:36 Setting VM storage...
2014/05/16 15:55:57 Done. Type `./boot2docker up` to start the VM.
sven:~$ ./boot2docker --vm=test up
2014/05/16 15:56:05 Waiting for SSH server to start...
2014/05/16 15:56:37 Started.
2014/05/16 15:56:37 To connect the Docker client to the Docker daemon, please set:
2014/05/16 15:56:37     export DOCKER_HOST=tcp://localhost:4243

init needs to pass on the non-default --vm, and then the up needs to realise that the NAT setting (which it could ask vbox for) is not that.

[SvenDowideit]

Also, there's no conflict detection between b2d vm's - so you can configure all of them to use the same NATed port, so long as they're not running.

[tianon]

Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).