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
There is a known issue with Docker Compose that makes it difficult to launch the containers in the correct order when migrations need to be run. Specifically, the error looks like:
$ docker-compose run --rm -e RAILS_ENV=production web rake db:migrateStarting autolabprod_db_1...Cannot start container 2ef8d589bdcce38d8d961a762cf934e0c0326c94d6b59827c05cf15f3e6b852f: Cannot link to a non running container: /autolabprod_db_1 AS /autolabprod_web_run_1/autolabprod_db_1
# start the db container
$ docker-compose up db
# --- wait for the output from initialization to appear to stop ---# --- quit the container with ^C ---# now finally launch everything
$ docker-compose up -d
The text was updated successfully, but these errors were encountered:
There is a known issue with Docker Compose that makes it difficult to launch the containers in the correct order when migrations need to be run. Specifically, the error looks like:
It is being tracked upstream at moby/moby#7445 and docker/compose#374.
The current workaround is to:
The text was updated successfully, but these errors were encountered: