zuul/tools/docker-compose.yaml
Clark Boylan 04ba835bf2 Switch our local testing docker-compose to mysql 8.0
Recently I debugged an issue that reproduced on mysql 8.0 on Jammy but
not my local system. It took quite some time for me to realize that
there was a difference in database versions which ended up being
an important detail. Update our docker-compose to better match what we
get in CI.

Change-Id: I7de268acb81680f3e6b7d3b1aa057e7babd3fa62
2023-01-31 16:29:04 -08:00

42 lines
910 B
YAML

version: "3"
services:
mysql:
container_name: zuul-test-mysql
image: mysql:8.0
environment:
- MYSQL_ROOT_PASSWORD=insecure_worker
ports:
- "${ZUUL_MYSQL_PORT:-3306}:3306"
tmpfs:
- /var/lib/mysql
volumes:
- "./mysqld.cnf:/etc/mysql/conf.d/mysqld.cnf:z"
postgres:
container_name: zuul-test-postgres
image: postgres
environment:
- POSTGRES_USER=openstack_citest
- POSTGRES_PASSWORD=openstack_citest
ports:
- "5432:5432"
tmpfs:
- /var/lib/postgresql/data
zookeeper:
container_name: zuul-test-zookeeper
user: "${USER_ID}"
image: zookeeper
environment:
- ZOO_AUTOPURGE_PURGEINTERVAL=1
- ZOO_LOG4J_PROP=WARN
ports:
- "2281:2281"
tmpfs:
- /data:uid=${USER_ID}
- /datalog:uid=${USER_ID}
volumes:
- "./ca:/var/certs:z"
- "./zoo.cfg:/conf/zoo.cfg:z"