clearlinux/rkt
2
0
Fork 0
mirror of https://github.com/clearlinux/rkt.git synced 2026-09-08 06:42:01 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #680 from coreos/robszumski-patch-1

Browse Source 
docs: link to metadata service document
This commit is contained in:
Jonathan Boulle
2015-03-26 13:52:37 -07:00
parent c4d0b1856e f4f2088a39
commit a4850abb30
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Documentation/commands.md
+1 -1
View File
@@ -257,7 +257,7 @@ The default networking configuration for Rocket is "host networking". This means
##### Private Networking
Another common configuration, "private networking", means the pod will be executed with its own network stack. This is similar to how other container tools work. The metadata service (launched via `rkt metadata-service`) must be running to use private networking.
Another common configuration, "private networking", means the pod will be executed with its own network stack. This is similar to how other container tools work. The [metadata service](metadata-service.md) (launched via `rkt metadata-service`) must be running to use private networking.
By default, Rocket private networking will create a loopback device and a veth device. The veth pair creates a point-to-point link between the container and the host. Rocket will allocate an IPv4 /31 (2 IP addresses) out of 172.16.28.0/24 and assign one IP to each end of the veth pair. It will additionally set a route for metadata service (169.254.169.255/32) and default route in the container namespace. Finally, it will enable IP masquerading on the host to NAT the egress traffic.