1. Help & Support
  2. Update and Migrate

Upgrading Hyperglance to a newer version

Note: After upgrading all user data will be retained, including authentication credentials, Rules, and tag-view keys.

Hyperglance is deployed as a VM image with 2 volumes attached. One for the Operating System and one for data. Running on that VM are a set of containers managed by a Docker-Compose file located at: /etc/docker-compose.yml


Hyperglance versions before v6.4: Make sure you run 'sudo docker logout' on the command line before attempting the upgrade.

If you use Hyperglance with AWS always check if a new service has been added and check if the IAM policies need updating (IAM Policy Requirements)

Release notes


To upgrade to the newest version of Hyperglance you must first pull down the latest docker images and then re-initialise the services using this command:

sudo docker logout && sudo docker-compose -f /etc/docker-compose.yml pull && sudo docker-compose -f /etc/docker-compose.yml up -d

NOTE: This requires Hyperglance to have internet in order to reach Docker Hub. If you wish to obtain access to repos on ECR or ACR please email support@hyperglance.com to request access.


To free up hard drive space you must now delete the old Docker images:

docker rmi $(docker images -a -q)

docker image prune


Scheduling Automatic Updates

If you want Hyperglance to automatically update you can set up a cron job in the Hyperglance VM. The example below sets the update to run once a day at midnight: 

sudo crontab -e

0 0 * * * /usr/bin/docker-compose -f /etc/docker-compose.yml pull &&  /usr/bin/docker-compose -f /etc/docker-compose.yml up -d

(Find examples of other cron expressions here: https://crontab.cronhub.io/ )