Repository navigation
Conversation
Since Engine 28.0.0, the bridge driver drops packets from remote hosts addressed to a container in a `nat` mode network, unless `trusted_host_interfaces` or `allow-direct-routing` allows them. The gateway modes section said published ports in `nat` networks are always reachable by direct routing. That contradicts the "Direct routing to containers in bridge networks" section and the example at the end of the same section. Signed-off-by: Cory Snider <csnider@mirantis.com>
The Ubuntu, Debian and Raspberry Pi OS install pages said firewall rules created with `nft` are not supported. With the experimental nftables firewall backend, "Docker with nftables" tells users to put their rules in their own nftables tables. Scope the iptables advice to the default backend and link to the nftables page. Signed-off-by: Cory Snider <csnider@mirantis.com>
With `com.docker.network.driver.mtu` unset or 0, the bridge driver does not set an MTU on the bridge or the container's veth pair. The interfaces keep the MTU the kernel gave them, which is 1500 for a veth device. "No limit" is not a possible MTU. Signed-off-by: Cory Snider <csnider@mirantis.com>
The note said automatic service discovery resolves only custom container names. On a user-defined network the daemon registers the container's name as a DNS name whatever its origin, generated names included (buildEndpointDNSNames in moby's daemon/container_operations.go), along with its aliases, short ID and hostname. Signed-off-by: Cory Snider <csnider@mirantis.com>
The kernel requirement said support for earlier kernels exists but is buggy. The ipvlan driver checks the kernel version when it creates a network, and returns an error on kernels older than 4.2. Signed-off-by: Cory Snider <csnider@mirantis.com>
`docker network prune` skips a local network only while it has endpoints, and a container has an endpoint only while it is running. "Networks which aren't used by any containers" reads as if a stopped container's network is kept. Signed-off-by: Cory Snider <csnider@mirantis.com>
Since Engine 29.8.0, Swarm ingress ports are published through the bridge driver's port mappings on docker_gwbridge, and the daemon deletes the DOCKER-INGRESS chains that earlier releases created. Drop the chain and the FORWARD jump to it from the list, and say which releases have it. Signed-off-by: Cory Snider <csnider@mirantis.com>
Since Engine 29.0.0, direct routing between bridge networks follows the same rules as direct routing from outside the host. The raw-PREROUTING rule that drops directly routed packets is only created in `nat` mode, and a `nat-unprotected` network accepts forwarded packets to any port. A `routed` network still drops packets to unpublished ports. The page said containers in other networks could not use direct routing to reach a `nat-unprotected` network, and that they could reach any port in a `routed` network. The `nat` bullet also names the two options that let containers in other networks use direct routing to its published ports: `allow-direct-routing`, and `trusted_host_interfaces` listing the other network's bridge. Signed-off-by: Cory Snider <csnider@mirantis.com>
✅ Deploy Preview for docsdocker ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Several Engine pages describe networking behavior that doesn't match the daemon. Each commit fixes one of them, and its message explains the daemon behavior it was checked against.
natnetwork unlessallow-direct-routingortrusted_host_interfacesallows it (Engine 28.0.0 and later).nat-unprotectednetwork, and only published ports in aroutednetwork (Engine 29.0.0 and later,moby/moby#49981).docker network prunealso removes networks that only stopped containers use.DOCKER-INGRESS, which Engine 29.8.0 and later don't create (moby/moby#53118).The commits are independent of each other. Please keep them separate when merging.
Generated by Claude Code