New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Official Flyway Dockerfile #797
Comments
Thanks for the suggestion. I'll look into this past Flyway 3.1 |
This would be great. A Flyway container could be started alongside the app container in Docker Compose, migrate the database at the injected hostname, then terminate totally independent of the app. |
You are welcome to use this as a starting point. |
@axelfontaine any chance we can get an official flyway repo in 2016? |
@dhoer Would you be willing to contribute your Dockerfile? |
Any update on this one ? |
This is now available: https://hub.docker.com/r/boxfuse/flyway/ Thanks @dhoer for providing a nice starting point with your repo! |
@axelfontaine Thanks for the official release! I do have to ask about why volumes were added. It prevents extending the image cleanly e.g.,
Unless there is a trick I don't know about, having volumes defined requires the use of multistage-build pattern, or repeating the entire contents of the dockerfile. Can volumes be removed from the dockerfile? They are easy to add and usage can be documented in readme. But once they are there, base images are hard to extend. |
@dhoer Good point. Fixed. In the future, please open a new issue against flyway/flyway-docker. Thanks! |
Would you consider establishing and supporting a Dockerfile for running flyway?
Here is a complete example that I am using in my own projects:
This allows you to run flyway inside of its own container. Example:
The text was updated successfully, but these errors were encountered: