mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-09-28 18:47:55 +00:00
5e94c95ad0
This was implemented by containers/netavark #1369; this commit completes the process by wiring it into Podman. We now respect the CLI order for configured networks - if a user passes `--net net1,net2` we guarantee that net1 will be configured before net2. For containers created before this patch, we don't retain enough information to configure networks in CLI order, so we use alphabetical order instead to still guarantee consistency. No breaking API changes have been made, but we do add a new field to supplement the existing map to (optionally) provide ordering information. The Podman CLI will always pass this. Existing applications that do not will, again, receive] deterministic ordering based on an alphabetical sort of network names. This requires the latest version of Netavark to work properly. Signed-off-by: Matthew Heon <matthew.heon@pm.me> |
||
|---|---|---|
| .. | ||
| createparse.go | ||
| ports.go | ||
| ports_test.go | ||
| specgen.go | ||
| specgenutil_test.go | ||
| specgenutil_windows_test.go | ||
| util.go | ||
| util_test.go | ||
| volumes.go | ||
| volumes_test.go | ||