These instructions are for users of our new Docker-based instance. If you run our older instances (or the old bootstrap script) check the legacy guide.
We recommended you upgrade your Redash instance to the latest release so you can benefit from new features and bug fixes. This document assumes you used our images to set up your instance of Redash.
For best results you should upgrade Redash by one semantic version at a time. To move from V4 to V7, for example, you should upgrade V4 to V5 to V6 to V7.
During each migration, check the releases page for any special notices or breaking changes in the next version.
Below is a table of recent docker release images for your reference:
If you are currently running an instance of Redash prior to V7, do not upgrade directly to V8. Upgrade semantically to V7 first. Read more about this on our forum here.
- Make sure to backup your data. You need to backup Redash’s PostgreSQL database (the database Redash stores metadata in, not the ones you might be querying) and your
.env file (if it exists). The data in Redis is transient.
- Change directory to
/opt/redash/docker-compose.yml Redash image reference to the one you want to upgrade to.
- Stop Redash services:
docker-compose stop server scheduler scheduled_worker adhoc_worker (you might need to list additional services if you updated your configuration)
- Apply migration (if necessary):
docker-compose run --rm server manage db upgrade
- Start services:
docker-compose up -d
Getting an error when running
Make sure the
ubuntu user is part of the
sudo usermod -aG docker $USER to add current user to the docker group.
- Logout and login again.