Open RussellLeVasseur opened 3 years ago
It looks like the mariadb container never actually starts.
Is it possible that you have missed to update the second istance of DB_PASS? The passwords in the environment sections for the containers osticket-app and osticket-db has to match in order to be able to establish a connection.
The database is quite sensitive, it breaks easily, so it's normal to recover a copy or start over.
It is advisable to have a UPS to avoid it "mine was in poor condition and broke 3 times in 1 week"
Are you running this from within WSL by any chance?
I ran into that issue as well. After debugging for some time, I noticed that it only happens if I run docker-compose from within WSL on a Windows machine.
Then, on separate machines, I ran docker-compose
directly in Windows and in Linux (no WSL), and it worked without any issues.
Also, going back to the original machine, if I first run docker-compose up
in Windows, then I shut it down, and then I run docker-compose up
in WSL, it also works.
I am still trying to figure it out, it seems it should be some config in WSL. Just letting you guys know in case you can reproduce it and figure it out more quickly than I would.
Used the example yml as written with password variables changed and seeing this error:
osticket-app | [WARN] ** [osticket] MySQL/MariaDB Server 'osticket-db' is not accessible, retrying..
I am not the best with docker networking to understand why.