Currently, the database (mysql or mariadb) may not start until after etherpad is already trying to start, in which case the etherpad instance fails to connect to the database, and exits immediately.
I've added wait-for-it to the entrypoint. It checks the database to see if the port is ready for connection. Once it is, the script proceeds as before.
Currently, the database (mysql or mariadb) may not start until after etherpad is already trying to start, in which case the etherpad instance fails to connect to the database, and exits immediately.
I've added
wait-for-it
to the entrypoint. It checks the database to see if the port is ready for connection. Once it is, the script proceeds as before.