containers reach network-online only with a dhcp lease, and bao users wait for it
This commit is contained in:
parent
04f8683f99
commit
81a57a9f81
1 changed files with 77 additions and 3 deletions
|
|
@ -56,6 +56,9 @@ The flows, end to end:
|
|||
|
||||
- **DHCP** — agent `dhcpcd` broadcasts on `eth0` → veth → bridge →
|
||||
host firewall (udp 67 hole) → dnsmasq pool → lease + router option.
|
||||
`dhcpcd` runs with `noipv4ll` and waits for an IPv4 address, so
|
||||
`network-online.target` means a lease, never a 169.254.x fallback; units
|
||||
that look up a swarm name at start order after it.
|
||||
- **DNS** — agents and the service containers query `bridgeIp:53`; dnsmasq
|
||||
answers hive zones authoritatively with the bridge IP, everything else
|
||||
forwards to the host's resolvers (see _Resolver behaviour_ below). Each
|
||||
|
|
|
|||
Loading…
Reference in a new issue