haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Remove comment about private networks only working with docker provider

This commit is contained in:
Brian Cain 2019-03-22 10:10:44 -07:00
parent f8744b66f0
commit 979dd37e46
No known key found for this signature in database
GPG Key ID: 9FC4639B2E4510A0
1 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
website/source/docs/docker/networking.html.md
View File

@ -31,15 +31,12 @@ there are no more containers using the network.
## Docker Network Options ## Docker Network Options
Only the network option `:private_network` is currently supported with the docker Most of the options given align with the command line flags
provider in Vagrant.
Most of the options given to `:private_network` align with the command line flags
for the [docker network create](https://docs.docker.com/engine/reference/commandline/network_create/) for the [docker network create](https://docs.docker.com/engine/reference/commandline/network_create/)
command. However, if you want the container to have a specific IP instead of using command. However, if you want the container to have a specific IP instead of using
DHCP, you also will have to specify a subnet due to how docker networks behave. DHCP, you also will have to specify a subnet due to how docker networks behave.
It should also be noted that if you want a specific IPv6 address, your `:private_network` It should also be noted that if you want a specific IPv6 address, your network
option should use `ip6` rather than `ip`. If you just want to use DHCP, you can option should use `ip6` rather than `ip`. If you just want to use DHCP, you can
simply say `type: "dhcp"` insetad. More examples are shared below which demonstrate simply say `type: "dhcp"` insetad. More examples are shared below which demonstrate
creating a few common network interfaces. creating a few common network interfaces.