From 5c50bd3063298ca544084e07be319bba351cadab Mon Sep 17 00:00:00 2001 From: Will Sargent Date: Thu, 13 Nov 2014 15:31:22 +0100 Subject: [PATCH] Add a more comprehensive warning. --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 44ca1ae..71c9872 100644 --- a/README.md +++ b/README.md @@ -66,7 +66,9 @@ Download Docker for OSX from the [Github Releases](https://github.com/boot2docke The canonical way to use Docker is with the aid of the boot2docker VM. However, using the out of the box boot2docker doesn't give me control over my Vagrant instances (especially the lack of port forwarding). So here's how to use boot2docker from a Vagrant instance. -We use the [YungSang modified boot2docker instance](https://github.com/YungSang/boot2docker-vagrant-box) from the [Vagrant Cloud](https://vagrantcloud.com/yungsang/boxes/boot2docker) -- this opens up port forwarding to the network, so is not safe on public wifi: +We use the [YungSang modified boot2docker instance](https://github.com/YungSang/boot2docker-vagrant-box) from the [Vagrant Cloud](https://vagrantcloud.com/yungsang/boxes/boot2docker) -- + +> NOTE: this opens up port forwarding to the network, so is not safe on public wifi. Some people consider docker without TLS to be [fundementally unsafe](https://medium.com/@kevanahlquist/never-run-docker-on-a-tcp-socket-without-tls-1e7df31cf18c). ``` mkdir ~/boot2docker