Fix bad behavior core tests by adding a custom subnet to the bw-docker network

This commit is contained in:
Théophile Diot 2023-07-04 16:26:54 -04:00
parent fccb25bee6
commit 08f9e5f20a
No known key found for this signature in database
GPG Key ID: E752C80DB72BB014
2 changed files with 10 additions and 3 deletions

View File

@ -15,6 +15,7 @@ services:
- "www.example.com:192.168.0.2"
networks:
bw-docker:
ipv4_address: 10.10.10.4
bw-services:
ipv4_address: 192.168.0.3

View File

@ -36,8 +36,9 @@ services:
DOCKER_HOST: "tcp://bw-docker:2375"
LOG_LEVEL: "info"
networks:
- bw-universe
- bw-docker
bw-universe:
bw-docker:
ipv4_address: 10.10.10.3
bw-docker:
image: tecnativa/docker-socket-proxy
@ -46,7 +47,8 @@ services:
environment:
CONTAINERS: "1"
networks:
- bw-docker
bw-docker:
ipv4_address: 10.10.10.2
networks:
bw-universe:
@ -63,3 +65,7 @@ networks:
- subnet: 192.168.0.0/24
bw-docker:
name: bw-docker
ipam:
driver: default
config:
- subnet: 10.10.10.0/24