mirror of
https://github.com/kernelkit/infix.git
synced 2026-08-06 23:43:20 +02:00
Joachim Wiberg
86df54c107
Usually the CNI bridge plugin "takes care" of enabling IPv4 forwarding on all interfaces, see issue #1125, but when the container tests are run in a different order from the infix_containers.yaml, Infix may reset the IPv4 forwarding on this critical interface. This change is both future proof and also ensures the test works as it was intended even if tests are run out-of-order. Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
=== Container with bridge network
==== Description
Verify connectivity with a simple web server container from behind a
docker0 bridge. As an added twist, this test also verifies content
mounts, i.e., custom index.html from running-config.
This also verifies port forwarding from container internal port to a
port accessed from the host.
==== Topology
ifdef::topdoc[]
image::{topdoc}../../test/case/infix_containers/container_bridge/topology.svg[Container with bridge network topology]
endif::topdoc[]
ifndef::topdoc[]
ifdef::testgroup[]
image::container_bridge/topology.svg[Container with bridge network topology]
endif::testgroup[]
ifndef::testgroup[]
image::topology.svg[Container with bridge network topology]
endif::testgroup[]
endif::topdoc[]
==== Test sequence
. Set up topology and attach to target DUT
. Create httpd container from bundled OCI image
. Verify container has started
. Verify DUT connectivity, host can reach 10.0.0.2
. Verify container is reachable on http://10.0.0.2:8080
<<<