Each time the admin container starts up, it runs some commands to make sure the mysql client is installed. This is annoying and wasteful. If we need it, we should install it in the Dockerfile, and eat the cost of the small increase in size. However, we *might* not need it if we switch to the supported way of initializing the database. From https://hub.docker.com/_/mysql/: When a container is started for the first time, a new database with the specified name will be created and initialized with the provided configuration variables. Furthermore, it will execute files with extensions .sh, .sql and .sql.gz that are found in /docker-entrypoint-initdb.d. Files will be executed in alphabetical order. You can easily populate your mysql services by mounting a SQL dump into that directory and provide custom images with contributed data. We might still need the mysql client for the upgrade script to work though?
This got fixed a part of the big rework in https://github.com/mozilla/balrog/pull/131.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.