Closed agcom closed 3 years ago
I also tested using the mariadb
image and it all worked fine!
Same issue here, trying to start the containers using docker-compose
but getting MySQL database domjudge not found on host mariadb; exiting
Note that you need to wait a bit the first time after starting mariadb before starting domjudge itself since the mariadb container needs some time for first boot
To point out, it seems domserver
is incompatible with mysql
.
So, the issue body saying "The commands at the docker image page seems not working" is false; They work fine, but, if you change the database image to
mysql
,domserver
startup will fail.
I was wondering if it's because of compatibility differences between MariaDB and MySQL?
DOMjudge should work with MySQL, but I have never tested it with the MySQL docker image. I will test it.
Found the issue. MySQL uses a sha2 password algorithm by default, which is not supported by our MariaDB client. Since we use Debian as base system in Docker, we can not install the MySQL version of the client libraries without external repositories.
The fix is to start the MySQL docker image with --default-authentication-plugin=mysql_native_password
.
Note that the migrations currently give an error since rank
seems to be a reserved keyword in MySQL but not MariaDB. We will try to fix this.
Above change together with this makes DOMjudge compatible with MySQL 8.0 again.
Hi! The commands at the docker image page seems not working.
Steps
Database container (using
mysql
image)Starts successfully and healthy.
DOMserver container
Fails with log,