How to update the Hyperglance application without Internet access

This process is useful when the Hyperglance VM does not have internet access to pull containers directory from DockerHub, and the helm chart from Github.

You will need SSH access to the Hyperglance VM and Docker running on your local PC or Mac.

On your local PC or Mac run the Hyperglance sandbox.

Note that we add an additional directory mapping in your current working directory to aid in extracting the airgap bundle required to perform the updates.
```
docker run --name hyperglance-sandbox -d \
--pull always \
--restart always \
--privileged \
-v hyperglance-data:/var/lib/data \
-v ./mapped:/mapped \
-p 443:443 \
hyperglance/sandbox:latest
```
Follow the by running the command docker logs hyperglance-sandbox --follow until you see Hyperglance starting, entering bash shell. You can now exist the logs by using Ctrl+C.
Enter the sandbox by running the command docker exec -it hyperglance-sandbox bash.

Run the command hg status to check if the Hyperglance deployment has come up.

hyperglance-sandbox: /
$ hg status
NAME                 READY   STATUS    RESTARTS   AGE
hyperglance-helm-0   3/3     Running   0          6m35s

Once Hyperglance is running, we can update the Hyperglance CLI to the latest version by running hg update-cli. The latest cli version tracks the latest supported versions of all the Hyperglance components.

hyperglance-sandbox: /
$ hg update-cli
[INFO] Current CLI version: 0.1.14
[ PLEASE WAIT ] ⠹ [ Updating CLI ][INFO] hg-cli-updater has been updated
[ PLEASE WAIT ] ⠴ [ Updating CLI ][INFO] cli update available — updating.
hyperglance-sandbox: /
$ hg version

▗▖ ▗▖▗▖  ▗▖▗▄▄▖ ▗▄▄▄▖▗▄▄▖  ▗▄▄▖▗▖    ▗▄▖ ▗▖  ▗▖ ▗▄▄▖▗▄▄▄▖
▐▌ ▐▌ ▝▚▞▘ ▐▌ ▐▌▐▌   ▐▌ ▐▌▐▌   ▐▌   ▐▌ ▐▌▐▛▚▖▐▌▐▌   ▐▌   
▐▛▀▜▌  ▐▌  ▐▛▀▘ ▐▛▀▀▘▐▛▀▚▖▐▌▝▜▌▐▌   ▐▛▀▜▌▐▌ ▝▜▌▐▌   ▐▛▀▀▘
▐▌ ▐▌  ▐▌  ▐▌   ▐▙▄▄▖▐▌ ▐▌▝▚▄▞▘▐▙▄▄▖▐▌ ▐▌▐▌  ▐▌▝▚▄▄▖▐▙▄▄▖

[INFO] Hyperglance CLI Version: 0.1.17
[INFO] Hyperglance CLI Commit Hash: 8cd2979
[INFO] Hyperglance App Version: 9.0.13
[INFO] Hyperglance App Commit Hash:  88b33390b24b1807c138f91e219c19b3686228c2
[INFO] Local Path Provisioner Version: v0.0.23

We can now generate the airgap bundle by running the command hg maintenance generate-all-bundle --distro rke2 --out /mapped/

hyperglance-sandbox: /
$ hg maintenance generate-all-bundle --distro rke2  --out /mapped/
[INFO] Generate K8s airgap bundle
[INFO] K8s bundle OK — rke2 v1.36.1+rke2r1
[INFO] Result: 
        Downloaded rke2 v1.36.1+rke2r1 assets
        Bundle created: /tmp/hg-all-bundle-1230471953/hg-airgap-k8s-rke2-v1.36.1_rke2r1.tar.gz
[INFO] Generate LPP airgap bundle
[INFO] LPP bundle OK — version v0.0.36
[INFO] Result: 
        Downloaded LPP v0.0.36 assets
        Bundle created: /tmp/hg-all-bundle-1230471953/hg-airgap-lpp-v0.0.36.tar.gz
[INFO] Generate Hyperglance airgap bundle
[INFO] HG bundle OK — chart version v9.0.13, 6 images
[INFO] Result: 
        Downloaded Hyperglance v9.0.13 assets
        Bundle created: /tmp/hg-all-bundle-1230471953/hg-airgap-hyperglance-9.0.13.tar.gz
[INFO] Generate CLI airgap bundle
[INFO] Result: 
        Pulled docker.io/hyperglance/updatetool:dev
        Bundle created: /tmp/hg-all-bundle-1230471953/hg-airgap-cli-dev.tar.gz
[INFO] Combine airgap bundles into mega bundle
[INFO] Result: 
        Mega bundle created: /mapped/hg-airgap-all-rke2-20260528T1144Z.tar.gz

The airgap bundle and its corresponding checksum file will be available in the ./mapped directory. Copy both of these files to the airgapped installation of Hyperglance. The default users home directory is a suitable location. Below is an example scp command, using the default user for our for our pre-built AWS AMI images.

scp -i <PATH_TO_SSH_KEY> mapped/* ec2-user@<INSTANCE_IP>:/home/ec2-user/

Once the files have been copied to the airgapped installation of Hyperglance, run the command sudo hg maintenance import-airgap-all-bundle --bundle-path <PATH_TO_UPLOADED_BUNDLE> to begin the upgrade process.

ec2-user@ip-10-0-10-198:~$ sudo hg maintenance import-airgap-all-bundle --bundle-path hg-airgap-all-rke2-20260528T1144Z.tar.gz
[WARN] The CLI update step exits immediately after updating the binary. Once the CLI has updated, re-run with --skip-cli to continue the remaining steps: 
sudo hg maintenance import-airgap-all-bundle -b <bundle-path> --skip-cli
[INFO] Import CLI bundle and update
[INFO] CLI image imported — starting update in background

PLEASE NOTE: The upgrade process starts with updating the cli to the version available in the bundle. The updater exits to complete the cli update process.

Once the cli has been updated, you can then run the command sudo hg maintenance import-airgap-all-bundle --bundle-path <bundle-path> --skip-cli to update the remaining components.

Please note the addition of the --skip-cli flag in this command. A successful upgrade will look like:

ec2-user@ip-10-0-10-198:~$ sudo hg maintenance import-airgap-all-bundle --bundle-path hg-airgap-all-rke2-20260528T1144Z.tar.gz --skip-cli
[INFO] Import K8s airgap bundle
[INFO] Taking pre-upgrade backup to /tmp/hg-pre-k8s-upgrade-20260528-124713.tar.gz…
[INFO] Create backup
[INFO] Result: 
        added original-values.yaml to backup bundle
        added values.yaml to backup bundle
        sanitised backup
[INFO] Stop Hyperglance
[INFO] Result: 
        Hyperglance was stopped
[INFO] Start Hyperglance
[INFO] Result: 
        Hyperglance started
[INFO] K8s bundle imported — now running rke2 v1.36.1+rke2r1
[INFO] Result: 
        K8s bundle imported successfully
[INFO] Update local-path-provisioner
[INFO] LPP updated to v0.0.36
[INFO] Result: 
        LPP updated successfully
[INFO] Import Hyperglance bundle and upgrade
[INFO] Result: 
        Bundle extracted
        Images imported
        Chart files copied
        Release "hyperglance" has been upgraded. Happy Helming!
NAME: hyperglance
LAST DEPLOYED: Thu May 28 12:56:47 2026
NAMESPACE: hyperglance
STATUS: deployed
REVISION: 3
NOTES:
+--------------------------------------------------------------------------------------------------------+
|    Welcome to                                                                                          |
|     _   ___   ______  _____ ____   ____ _        _    _   _  ____ _____                                |
|    | | | \ \ / /  _ \| ____|  _ \ / ___| |      / \  | \ | |/ ___| ____|                               |
|    | |_| |\ V /| |_) |  _| | |_) | |  _| |     / _ \ |  \| | |   |  _|                                 |
|    |  _  | | | |  __/| |___|  _ <| |_| | |___ / ___ \| |\  | |___| |___                                |
|    |_| |_| |_| |_|   |_____|_| \_\\____|_____/_/   \_\_| \_|\____|_____|                               |
|                                                                                                        |
|    ===================================                                                                 |
|    Hyperglance Marketplace Deployment.                                                                 |
|    ===================================                                                                 |
|                                                                                                        |
|    Listening on port 443 (HTTPS).                                                                      |
|                                                                                                        |
|    HOW TO CONNECT                                                                                      |
|        1. Get the Public IP of this VM                                                                 |
|        2. Visit https://<PublicIP> in your browser                                                     |
|                                                                                                        |
|        Note: Please allow up to 5 minutes for the Hyperglance WebUI to become available.               |
|                                                                                                        |
|    DEFAULT LOGIN CREDENTIALS                                                                           |
|        Default User: admin                                                                             |
|        Default Password for AWS: The InstanceID of this instance.                                      |
|        Default Password for Azure: The 'Computer Name' of this VM.                                     |
|        Default Password for GCP: The instance-id of the VM instance e.g.  2531258160337713584          |
|                                                                                                        |    
+--------------------------------------------------------------------------------------------------------+
[INFO] 
   _____ _    _  _____ _____ ______  _____ _____ _ 
  / ____| |  | |/ ____/ ____|  ____|/ ____/ ____| |
 | (___ | |  | | |   | |    | |__  | (___| (___ | |
  \___ \| |  | | |   | |    |  __|  \___ \\___ \| |
  ____) | |__| | |___| |____| |____ ____) |___) |_|
 |_____/ \____/ \_____\_____|______|_____/_____/(_)
The migration has completed successfully. It is highly recommended that you perform a reboot.
If you created any backups in the /tmp directory, it is recommended that you copy these to a safe location as they could be wiped on reboot.

Reboot the instance. Once the instance is back up, wait for hg status shows the hyperglance-helm-0 pod as running. Then run hg version to confirm the updated versions.

ec2-user@ip-10-0-10-198:~$ hg status
NAME                 READY   STATUS    RESTARTS        AGE
hyperglance-helm-0   3/3     Running   3 (7m19s ago)   14m
ec2-user@ip-10-0-10-198:~$ hg version
▗▖ ▗▖▗▖  ▗▖▗▄▄▖ ▗▄▄▄▖▗▄▄▖  ▗▄▄▖▗▖    ▗▄▖ ▗▖  ▗▖ ▗▄▄▖▗▄▄▄▖
▐▌ ▐▌ ▝▚▞▘ ▐▌ ▐▌▐▌   ▐▌ ▐▌▐▌   ▐▌   ▐▌ ▐▌▐▛▚▖▐▌▐▌   ▐▌   
▐▛▀▜▌  ▐▌  ▐▛▀▘ ▐▛▀▀▘▐▛▀▚▖▐▌▝▜▌▐▌   ▐▛▀▜▌▐▌ ▝▜▌▐▌   ▐▛▀▀▘
▐▌ ▐▌  ▐▌  ▐▌   ▐▙▄▄▖▐▌ ▐▌▝▚▄▞▘▐▙▄▄▖▐▌ ▐▌▐▌  ▐▌▝▚▄▄▖▐▙▄▄▖

[INFO] Hyperglance CLI Version: 0.0.17
[INFO] Hyperglance CLI Commit Hash: eaa5fc3
[INFO] Hyperglance App Version: 9.0.13
[INFO] Hyperglance App Commit Hash:  88b33390b24b1807c138f91e219c19b3686228c2
[INFO] RKE2 Version: v1.36.1+rke2r1
[INFO] Local Path Provisioner Version: v0.0.36

How to update the Hyperglance application without Internet access

This article describes how to update the Hyperglance application by downloading the Hyperglance Sandbox which contains the Hyperglance CLI, which is used to create an airgap bundle.