Nicolas De Loof 54caa0775c test(e2e): pull and network scenarios ... - pull: the CLI's Pulled/Skipped report is the observable, so the five scenarios (always-pull, present-locally, build-only, failure, --ignore-pull-failures) legitimately match output; models are inline and the whole compose-pull fixture tree — including the orphaned duplicate-images directory no test referenced — is removed. - networks: aliases, links, ipam, network_mode: service, subnet change, mac_address and interface_name become scenarios. The subnet-change scenario locks what actually happens: the network is replaced but the container is reconnected, not recreated (NotRecreated), which the legacy test never distinguished. TestNetworks (fixed host ports, HTTP fixture services) and TestNetworkRecreate (OR-shaped output assertion) stay legacy. Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>		2026-08-18 16:49:56 +02:00
..
compose.yaml