-
Notifications
You must be signed in to change notification settings - Fork 32
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
How can I upgrade metabase avoiding any data loss? #2
Comments
I've tested just running docker-compose down and after that pulled the latest version from https://hub.docker.com/r/metabase/metabase and at the end, I've changed the version inside the docker-compose.yml file I've tested different versions using the tags to get the image... If I downgrade the image I get some errors related to tables which are not existents in the database depending where I'm navigating but if I do an upgrade seems the migrations take care about the new tables needed to be created. Can it be done this way or am I just being lucky and there really hasn't been any change in the metabase db tables since version 0.41? |
Hi @tonytmt sudo docker-compose down sudo docker-compose up -d Have a nice day ;) |
Hello and thank you very much for your tutorial.
All is running pretty well...
One question that I need help with is upgrading the metabase image without any data loss.
They have just updated to version v0.42 (https://www.metabase.com/docs/v0.42/)
https://www.metabase.com/docs/latest/operations-guide/upgrading-metabase.html
Is possible to just compose down and compose up again as your tutorial says or I need to modify something else?
Thank you
The text was updated successfully, but these errors were encountered: