Docker For Mac Multiple Machines

Using Docker Machine (usually through Docker Toolbox) to run locally only if you have an older Mac version that isn't supported, which isn't the case here, or a Windows machine without Windows 10 pro. Kerio connect for outlook mac. The only other case you need Docker Machine is for controlling remote machines or setting up multiple nodes locally. Docker Machine overview Install Docker Machine Install a machine on your local system using VirtualBox Install multiple machines on your cloud provider Digital Ocean Example AWS Example Machine concepts.

Expected behavior Support for 'docker swarm' commands in Docker for Mac so that one can create a multi-node swarm and use the new orchestration features of Docker 1.12 Actual behavior Currently the swarm init command will register a swarm using the IP address of the Docker host running on the hypervisor which will not be accessible from another machine. Information Current version in use 1.12.0 build 81071 Steps to reproduce the behavior Follow the steps in this tutorial but using Macs instead of VM's. I have this problem too, apparently. When I create a new swarm using docker swarm init --advertise-addr 10.0.1.22 on my Mac (where 10.0.1.22 is an IP of the Mac itself), I'll get the following error: Error response from daemon: advertise address must be an IP address or network interface (with optional port number) When I run init without --advertise-addr, I'll get the following output: Swarm initialized: current node (96nk3rf2baoracyrmilmjmzf7) is now a manager. To add a worker to this swarm, run the following command: docker swarm join --token SWMTKN-1-5mdvml1wp7wzv318qymzqi8rgg6w6j3ma904nkrq7f33ndd0b4-d670pkto548caentg2aoehjkm 192.168.65.2:2377 The IP 192.168.65.2 apparently is the IP of the docker engine/hypervisor (not sure yet how the new architecture works in detail on OS X, yet). This IP unfortunately can't be accessed from outside the machine like OP said, from another machine on the network. The second problem is, that I can't assign an IP from my machine to work around this, rendering the swarm commands rather useless in my case.

And worse: the tutorials and documentation is not consistent with what actually happens. Am I doing something wrong or is this a bug?

Personally I was just experimenting but I think using Docker for Mac would be a much better experience than docker-machine when you want to show someone how to use swarm on multiple physical machines. As noted in later comments it would be great if the swarm tutorial was clear that you have to use docker-machine and that it is safe to do so. As a use of the Docker for Mac Beta I often ended up in a messed up state because of running different docker-machine versions and so on. That made me wary to try to use both at once. I think even in production environments people would like to be able to connect a local laptop to a swarm cluster. For example Weaveworks lets you do this. I mentioned my problems in twitter exchange with Justin Cormack who recommended opening this ticket.