From 0d8a5a46df1503d6bb9d03e11b9cd8ffc4d153b6 Mon Sep 17 00:00:00 2001 From: Trevor Allen Date: Mon, 26 Nov 2018 08:50:38 -0500 Subject: [PATCH] Add network-routing clarification to comparison Add a line to comparison mentioning that docker-for-mac doesn't support routing traffic to containers. --- docker-for-mac/docker-toolbox.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docker-for-mac/docker-toolbox.md b/docker-for-mac/docker-toolbox.md index 8c846363a3..7d900c8611 100644 --- a/docker-for-mac/docker-toolbox.md +++ b/docker-for-mac/docker-toolbox.md @@ -62,6 +62,9 @@ With Docker for Mac, you only get (and only usually need) one VM, managed by Doc for Mac. Docker for Mac automatically upgrades the Docker client and daemon when updates are available. +Also note that Docker for Mac can’t route traffic to containers, so you can't +directly access an exposed port on a running container from the hosting machine. + If you do need multiple VMs, such as when testing multi-node swarms, you can continue to use Docker Machine, which operates outside the scope of Docker for Mac. See [Docker Toolbox and Docker for Mac