spiegel_podman/vendor/github.com/containerd
Matthew Heon 5e94c95ad0 Move to deterministic network setup order
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>
2026-04-17 10:00:32 -04:00
..
errdefs vendor: update c/{common, image, storage} to latest main 2025-08-26 10:02:35 +02:00
log vendor latest c/common 2023-10-10 17:08:04 +02:00
platforms Move to deterministic network setup order 2026-04-17 10:00:32 -04:00
stargz-snapshotter/estargz Vendor common test for artifact digest lookup 2026-01-26 15:45:56 -06:00
typeurl/v2 Add newer c/i to support artifacts 2025-01-08 13:42:24 -06:00