Development database from the repository's compose file cannot start in the account
The service shlink_db_mysql did not start (unhealthy), so the application was not started either. It printed: 0 [ERROR] [MY-010460] [Server] --initialize specified but the data directory exists and is not writable. Aborting. 0 [ERROR] [MY-013236] [Server] The designated data directory /var/lib/mysql/ is unusable. You can remove all files that the server added to it. 0 [ERROR] [MY-010119] [Server] Aborting 0 [System] [MY-010910… The full output is in the deploy log.
Why it happens
The repository's compose file is a development environment that runs every database the project is tested against. The engine kept all of them next to the application. The MySQL one runs as a fixed user on a data directory inside the checkout that it cannot write, and the application waits for it.
What the log looks like
error: service shlink_db_mysql did not start (unhealthy): 0 [ERROR] [MY-010460] [Server] --initialize specified but the data directory exists and is not writable. Aborting. 0 [ERROR] [MY-013236] [Server] The designated data directory /var/lib/mysql/ is unusable. You can remove all files that the server added to it. 0 [ERROR] [MY-010119] [Server] Aborting 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.46) MySQL Community Server - GPL. 2026-10-02 03:04:13+00:00 [No…Container shlink_db_mysql Error dependency shlink_db_mysql failed to startdependency failed to …