When you're ready to upgrade, you'll load the new Docker image and run the upgrade script. Your data is not affected by this process.
What does the upgrade script do? The upgrade.sh script pulls the new image into the running stack and restarts the application containers. It does not run docker compose down on your whole stack, and it does not remove or recreate named volumes — your data volumes (dradis-credentials, dradis-storage, dradis-storage-public, mysql-data) are untouched. Any compose.override.yaml customisations you have in place are preserved.
dradis-pro-5.xx.0-assess.tar.gz.deployer, and load it:
scp dradis-pro-5.xx.0-assess.tar.gz deployer@[host]:. ssh deployer@[host] docker image load < dradis-pro-5.xx.0-assess.tar.gz
docker image tag dradis-pro:5.[old].0 dradis-pro:previousDo not remove the previous image yet; you'll need it if you need to roll back.
latest, replacing 5.xx.0 with the version that was just loaded.
docker image tag dradis-pro:5.xx.0 dradis-pro:latest
chmod +x upgrade.sh ./upgrade.sh
/pro in your browser and check the footer to confirm that the update was successful.If something goes wrong, you can roll back to the previous version:
latest tag back at the previous image:
docker image tag dradis-pro:previous dradis-pro:latestwhere
:previous is whatever you tagged the previous image before.
./upgrade.sh
Next help article: Migrate your data to a new Dradis Pro container →
Last updated by Christoffer Bjørk Pedersen on 2026-05-11
Loading form...
Your email is kept private. We don't do the spam thing.