-
Notifications
You must be signed in to change notification settings - Fork 18.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding custom bridge support to docker run #6704
Changes from all commits
3f4837d
f7a4aae
7a3a377
c8f413b
30e9d8b
8433b4b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -131,10 +131,11 @@ PID files): | |
|
||
--dns=[] : Set custom dns servers for the container | ||
--net="bridge" : Set the Network mode for the container | ||
'bridge': creates a new network stack for the container on the docker bridge | ||
'none': no networking for this container | ||
'container:<name|id>': reuses another container network stack | ||
'host': use the host network stack inside the container | ||
'bridge': creates a new network stack for the container on the default docker bridge | ||
'bridge:<name>': creates a new network stack for the container on the specified pre-existing bridge | ||
'none': no networking for this container | ||
'container:<name|id>': reuses another container network stack | ||
'host': use the host network stack inside the container | ||
|
||
By default, all containers have networking enabled and they can make any | ||
outgoing connections. The operator can completely disable networking | ||
|
@@ -170,6 +171,16 @@ container's namespaces in addition to the `loopback` interface. An IP | |
address will be allocated for containers on the bridge's network and | ||
traffic will be routed though this bridge to the container. | ||
|
||
#### Mode: bridge:<name> | ||
With the networking mode set to `bridge:<name>` a container will use a | ||
pre-existing bridge referred to by `name` for its networking setup. | ||
A pair of veth interfaces will be created in bridge `name` for the container. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. should this be vEth instead of veth, or even "virtual ethernet (vEth)" for example? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Agreed, I think "virtual ethernet (vEth)" is clearest. |
||
One side of the veth pair will remain on the host attached to the bridge while | ||
the other side of the pair will be placed inside the container's namespaces in | ||
addition to the `loopback` interface. An IP address will be allocated for | ||
containers on the bridge's network and trafic will be routed though this bridge | ||
to the container. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
|
||
#### Mode: host | ||
|
||
With the networking mode set to `host` a container will share the host's | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know in the generated docs, but the output looks weird (tabs/spaces)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.