ltangvald
ltangvald
Right. Currently the entrypoint script only tries to ensure correct ownership of datadir. We can't account for every config customization, though we could add checks for some of the major...
Yes, I'll submit an issue/pr upstream
I would say it's intentional, but possibly not fully thought through (the basic idea is to remove binaries that aren't needed for the docker images). I'll get a review done...
For mysqlcheck it's partially a case of it being significantly less useful for innodb than it was for myisam, and that the checking functionality it still supports can be done...
I think we've discussed using printf %q to sanitize the password before, but iirc there was some case where it would break.
Did you try running just the mysql_upgrade command? i.e. docker run [params] mysql:latest mysql_upgrade I see this might have permission issues, since the entrypoint script will only try to ensure...
Hi, In general, you can pick which command is run on an image by adding it to the end of the run command. The default for the mysql image is...
I only really considered a major upgrade such as 5.6 to 5.7, but our docs do recommend always running mysql_upgrade for any new version. We may want to try to...
We could store the version with the database, maybe. The init script could compare the version in the file with the current database, and run mysql_upgrade if they differ (and...
Yes, mysql_upgade is simply a client, so it needs to connect to a running server with admin credentials. It _should_ be completely non-destructive, but I'll ask around a bit to...