Skip to content
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

First run of docker-compose fails as database hasn't been fully initialised when migration script runs #1

Closed
simondrake opened this issue Aug 1, 2021 · 1 comment
Labels
bug Something isn't working
Projects

Comments

@simondrake
Copy link
Contributor

simondrake commented Aug 1, 2021

Upon running docker-compose up -d for the very first time, the below error will be observed

trackmyfish_migrations    | 2021/08/01 19:08:42 error creating new migration: dial tcp 172.26.0.2:5432: connect: connection refused

This is because, when the migrations are run, the database hasn't been fully initialised. Running docker-compose up -d again, after a minute or two, will work.

@simondrake simondrake added the bug Something isn't working label Aug 1, 2021
@simondrake simondrake added this to To do in TrackMyFish via automation Aug 1, 2021
@simondrake
Copy link
Contributor Author

Fixed by TrackMyFish/db#11

TrackMyFish automation moved this from To do to Done Nov 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

1 participant