You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does anyone know what would cause this error when running the Flyway container? I started seeing it after doing a Docker system prune. I'm running on Windows 10 64bit with Docker Desktop and the Ubuntu subsystem, in case it matters. It happens with both the alpine
$ docker run --rm -v .:/flyway/sql redgate/flyway:10.5.0 -url=jdbc:postgresql://postgres/ -user=postgres migrate
WARNING: This version of Flyway is out of date. Upgrade to Flyway 10.6.0: https://rd.gt/3rXiSlV
Flyway Community Edition 10.5.0 by Redgate
See release notes here: https://rd.gt/416ObMi
ERROR: Unknown configuration properties: SOURCES,CSOURCES
The text was updated successfully, but these errors were encountered:
I eventually figured out that my bind mount (-v) is invalid. Once I fixed the local mount path, the Flyway container started working again.
The "Unknown configuration properties" error is pretty unintuitive. It would be better if Flyway would verify that it can find the SQL scripts before starting migration.
bburtin
changed the title
ERROR: Unknown configuration properties: SOURCES,CSOURCES
Unintuitive error when bind mount is invalid
Jan 16, 2024
bburtin
changed the title
Unintuitive error when bind mount is invalid
Unintuitive error when bind mount directory is invalid
Jan 16, 2024
Hi @bburtin The issue here seems to be happening before Flyway attempts the migration. The message ERROR: Unknown configuration properties: SOURCES,CSOURCES indicates that it has identified something as a configuration file which contains the properties SOURCES and CSOURCES which it does not understand. Unfortunately, from the information provided above I would not be able to tell what it is mistakenly thinking is a config file
Does anyone know what would cause this error when running the Flyway container? I started seeing it after doing a Docker system prune. I'm running on Windows 10 64bit with Docker Desktop and the Ubuntu subsystem, in case it matters. It happens with both the alpine
The text was updated successfully, but these errors were encountered: