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

Fix subnet to ip_range and add gateway information for public networks

This commit is contained in:
Chris Roberts 2019-03-25 15:26:18 -07:00
parent 1e856ecf8a
commit 8339e63423
1 changed files with 16 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -106,16 +106,26 @@ the first active interface when setting up the network:
docker.vm.network :public_network, type: "dhcp", bridge: ["eth0", "wlan0"] docker.vm.network :public_network, type: "dhcp", bridge: ["eth0", "wlan0"]
``` ```
Finally, the subnet for the bridge interface must be known when setting up The available IP range for the bridge interface must be known when setting up
the docker network. Even though a DHCP service may be available on the public the docker network. Even though a DHCP service may be available on the public
network, docker will manage IP addresses provided to containers. This means network, docker will manage IP addresses provided to containers. This means
that the subnet provided when defining the network should not be included that the subnet provided when defining the available IP range for the network
within the subnet managed by the DHCP service. Vagrant will prompt for subnet should not be included within the subnet managed by the DHCP service. Vagrant
information, however, it can also be provided in the Vagrantfile using the will prompt for the available IP range information, however, it can also be
`subnet` option: provided in the Vagrantfile using the `docker_network__ip_range` option:
```ruby ```ruby
docker.vm.network :public_network, type: "dhcp", bridge: "eth0", subnet: "192.168.1.252/30" docker.vm.network :public_network, type: "dhcp", bridge: "eth0", docker_network__ip_range: "192.168.1.252/30"
```
Finally, the gateway for the interface is required during setup. The docker
provider will default the gateway address to the first address available for
the subnet of the bridge device. Vagrant will prompt for confirmation to use
the default address. The address can also be manually set in the Vagrantfile
using the `docker_network__gateway` option:
```ruby
docker.vm.network :public_network, type: "dhcp", bridge: "eth0", docker_network__gateway: "192.168.1.2"
``` ```
More examples are shared below which demonstrate creating a few common network More examples are shared below which demonstrate creating a few common network