[satlab]: Run drone on Satlab network instead of host
Servod Container uses default_satlab network set by satlab-compose,
where as drone is running on host network. This resulted in conflict with
the network interface. Changed Drone to use default_satlab network
to fix this issue. Also set a static IP for the drone otherwise the compose
assigns an arbitary ip address which might conflict with other docker containers
Change-Id: I0ae3cb6dfbb73abb0816aab0bacbbd45f17d8c73
Bug: b/200173380
Test: Manual
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/satlab/+/3165886
Commit-Queue: Prasad Vuppalapu <prasadv@chromium.org>
Tested-by: Prasad Vuppalapu <prasadv@chromium.org>
Reviewed-by: Anh Le <anhdle@chromium.org>
diff --git a/src/dockerfiles/compose/docker-compose.yaml b/src/dockerfiles/compose/docker-compose.yaml
index fd946ed..0ea89fb 100644
--- a/src/dockerfiles/compose/docker-compose.yaml
+++ b/src/dockerfiles/compose/docker-compose.yaml
@@ -31,13 +31,18 @@
- DOCKER_DRONE_LABPACK_DIR=/usr/local/labpack
- DOCKER_DRONE_CACHESERVER_IP=192.168.100.1
privileged: true
- network_mode: "host"
hostname: ${DRONE_HOSTNAME:-satlab-drone}
restart: always
volumes:
- ssp:/usr/local/autotest/containers/ssp_volume:rw
- service_accounts:/creds/service_accounts:rw
- /var/run/docker.sock:/var/run/docker.sock:rw
+ # TODO (prasadv): Make static ip addresses higher numbers
+ # so that the lower number are available for dhcp to assign it
+ # to dynamically created containers such as servod container
+ networks:
+ satlab:
+ ipv4_address: 192.168.100.10
dns:
- 192.168.100.51
depends_on:
