a month ago
I want to create a DB service of MySQL version 5.7 (via CLI if possible) in US East (Virginia).
Now i tried to create a db mysql service, which created it with version 9.4, then i changed the version to 5.4 but it crashes, and even if it get's deployed the database doesn't work due to missing files or something which happens because we can't downgrade the mysql version.
There is a workaround, maybe. which is after successful deployment with version 9.4, stop the service, detach/remove the volume and then trigger the deployment again with 5.7 version but, there's some issues
you can't stop the service, the only option you have is to remove the service
after removing the service when you create again it will be version 9.4 only as before
you can't remove the volume without removing the service
So if anyone can help me out, it will a great help.
Thank You
6 Replies
a month ago
Have you tried creating a service manually and using MySQL’s 5.7 image tag?
a month ago
Another option, would be to try deploying the MySQL template with 9.4, change it to the desired version (for example 5.4) and wipe the volume afterwards. This way, it should no longer complain that the volume is already initialized with a different MySQL version. (It will still crash once when you change the tag to 5.4, but should deploy fine once you have wiped the volume).
yes i tried this but it crashes every time, no matter how many times i redeploy it or wipe the volume
25 days ago
Deploy a docker image with the following tag:mysql:5.7
Make sure to configure the required variables (password, username, etc)