flyway-docker
flyway-docker copied to clipboard
`flyway/flyway:10.7.1-alpine`: no longer able to connect to a MySQL database
Prior to the latest release, I was able to connect to a database just fine, but now I get the following error:
2024-02-01T14:24:41.397721480Z WARNING: Storing migrations in 'sql' is not recommended and default scanning of this location may be deprecated in a future release
2024-02-01T14:24:41.397785102Z Flyway OSS Edition 10.7.1 by Redgate
2024-02-01T14:24:41.397815732Z
2024-02-01T14:24:41.397820389Z See release notes here: https://rd.gt/416ObMi
2024-02-01T14:24:41.425870927Z ERROR: Unable to connect to jdbc:mysql://gse-database:3306/gse?serverTimezone=UTC&useLegacyDatetimeCode=false&useUnicode=yes&characterEncoding=UTF-8&allowPublicKeyRetrieval=true
Compose file in question: https://github.com/seart-group/ghs/blob/master/docker-compose/docker-compose.yml. The settings from this file worked fine for every previous version.
Looks like the same issue as #135
We're investigating a proper solution, but try adding &permitMysqlScheme=true
as a workaround for now.
Looks like the same issue as #135
I did not see it, thank you for letting me know.
We're investigating a proper solution, but try adding
&permitMysqlScheme=true
as a workaround for now.
I'll try this out, but I'll wait for a proper fix before we roll out this version into production.
Looks like the same issue as #135
We're investigating a proper solution, but try adding
&permitMysqlScheme=true
as a workaround for now.
Just thought I'd let everyone know the workaround does indeed work. This seems to me like an issue that stems from a limitation of the MariaDB connector. Not sure if you guys intend on providing a patch, but it did work in prior versions without the URL parameter.