fix: use 10.200.0.0/24 subnet (172.16.0.0/16 is host network)

This commit is contained in:
Claus Lohmar 2026-07-10 22:09:46 +01:00
parent 634cab3464
commit 9083119aca
2 changed files with 4 additions and 4 deletions

View file

@ -18,7 +18,7 @@ services:
retries: 3
networks:
nextwks-net:
ipv4_address: 172.16.0.10
ipv4_address: 10.200.0.10
authelia:
image: git24hcom/authelia:latest
@ -37,7 +37,7 @@ services:
retries: 3
networks:
nextwks-net:
ipv4_address: 172.16.0.11
ipv4_address: 10.200.0.11
launcher:
image: alpine:latest
@ -59,7 +59,7 @@ services:
retries: 3
networks:
nextwks-net:
ipv4_address: 172.16.0.12
ipv4_address: 10.200.0.12
networks:
nextwks-net:

View file

@ -98,7 +98,7 @@ if [ "$GREENFIELD" = true ]; then
# Podman network + deploy stack
echo "[5/5] Deploying containers on $NETWORK_NAME..."
podman network create --subnet 172.16.0.0/24 "$NETWORK_NAME" 2>&1 || true
podman network create --subnet 10.200.0.0/24 "$NETWORK_NAME" 2>&1 || true
podman-compose -f "$TARGET_DIR/compose/stack.yaml" down 2>/dev/null || true
podman-compose -f "$TARGET_DIR/compose/stack.yaml" up -d 2>&1 || echo "[WARN] Stack deploy had issues"