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
I noticed that database migrations are not automatic in docker. For those of us who automate our docker upgrades, or perhaps don't pay attention after pulling new image, this causes the container to silently fail (the node drops out) and the container will stop if a database migration is required.
I've seen the related issue #3145, and I'd suggest instead that --upgradeshould be the default arg.
Instead, for the (few?) use cases where migrations are not wanted, the use of static tags to stay on previous builds, or manually overriding of the docker CMD should be preferred.
In my own case, I have now added start --upgrade to the container startup args to cover this scenario, so at a minimum this should be added to documentation as a recommended start-up command for the average user.
Version
0.1.68
Debug output
No response
Relevant log output
No response
Graffiti
tjb_altf4
The text was updated successfully, but these errors were encountered:
What happened?
I noticed that database migrations are not automatic in docker. For those of us who automate our docker upgrades, or perhaps don't pay attention after pulling new image, this causes the container to silently fail (the node drops out) and the container will stop if a database migration is required.
I've seen the related issue #3145, and I'd suggest instead that
--upgrade
should be the default arg.Instead, for the (few?) use cases where migrations are not wanted, the use of static tags to stay on previous builds, or manually overriding of the docker CMD should be preferred.
In my own case, I have now added
start --upgrade
to the container startup args to cover this scenario, so at a minimum this should be added to documentation as a recommended start-up command for the average user.Version
0.1.68
Debug output
No response
Relevant log output
No response
Graffiti
tjb_altf4
The text was updated successfully, but these errors were encountered: