Open soeren-helbig opened 6 years ago
I believe this is due to some issues with naming/service discovery with docker compose or docker stack deploy. I was using docker stack deploy to run this in swarm, and I found I needed to add an alias, matching DB_SERVICE_NAME.
Provided you had a pre-existing network named "database" (docker network create -d overlay --subnet=172.100.100.0/24 database
) your docker-compose.yml may need to look like this..
version: "3"
services:
database:
image: toughiq/mariadb-cluster:10.1
environment:
DB_SERVICE_NAME: database
MYSQL_ROOT_PASSWORD: 12345678
MYSQL_DATABASE: test
MYSQL_USER: test
MYSQL_PASSWORD: 12345678
networks:
database:
aliases:
- database
I can't guarantee that you're hitting the same problem I was, but it looks similar. I'm actually hoping to write up a blog post about this specific issue so hopefully I can remember to come back here and link it...
First of all, thanks for your work. If this one is running, it would be a very nice piece of my docker toolkit. But actually use with the following docker-compose file fails
running
docker-compose up database
gives me the following outputAm i doing wrong? Can i provide some more output to help you fixing the issue?