Closed dlitz closed 10 years ago
...default.
The Docker port allows arbitrary remote code execution inside the VM, so we don't want that turned on by default.
Unfortunately, this is still going to be a problem for users of the vmware_fusion provider, since it apparently ignores the :host_ip parameter:
https://github.com/mitchellh/vagrant/issues/3916
Adding :id => "docker" allows downstream users of the box to disable the port-forward using something like this in their Vagrantfile:
config.vm.network "forwarded_port", guest: 4243, host: 4243, id: "docker", disabled: true
@dlitz dang, didn't know about the id: trick, in fact I was in that code a few weeks ago to disable this very thing.
id:
...default.
The Docker port allows arbitrary remote code execution inside the VM, so we don't want that turned on by default.
Unfortunately, this is still going to be a problem for users of the vmware_fusion provider, since it apparently ignores the :host_ip parameter:
Adding :id => "docker" allows downstream users of the box to disable the port-forward using something like this in their Vagrantfile: