Skip to main content
Version: 029-rc4

Install remotely via Pantahub

Pantahub is the cloud backend for Pantavisor. Once a device is claimed, you can push application updates to it from anywhere — the device polls Pantahub and applies the new revision automatically.

1 — Claim Your Device​

Before remote management is possible, the device must be registered in your Pantahub account. The device prints a one-time challenge token and its device ID on boot.

Read them from the device console (serial or SSH):

cat /pv/challenge
# pleasantly-finer-unicorn

cat /pv/device-id
# 5b582638c67920b9de2

Log in to hub.pantacor.com, go to Claim Device, and enter the device ID and challenge. Once claimed, the device appears in your device list and its status updates in real time.

See Remote access via Pantahub for the canonical claiming and remote-access walkthrough.

2 — Build the Container Package​

On your workstation, build the container you want to install using pvr. If you have not done this yet, follow the steps in the pvtx install guide to create a myapp.tar.gz bundle.

3 — Deploy via Pantahub​

From the device dashboard on hub.pantacor.com:

  1. Click the device name to open its detail view.
  2. Go to the Manage tab.
  3. Click Begin Transaction.
  4. Click Upload New Part and select your myapp.tar.gz file.
  5. Enter a commit message and click Commit Transaction.

Pantahub queues the update. The device polls for new revisions periodically and downloads the changed container objects as a diff (only the objects that changed are transferred). It then applies the new revision.

Or via the pvr CLI​

You can also push the revision from your workstation instead of the dashboard: pvr clone https://pvr.pantahub.com/USERNAME/DEVICE_NAME, make your changes, then pvr add ., pvr commit and pvr post. See Remote access via Pantahub for the full remote workflow.

4 — Monitor the Update​

The device dashboard shows the update progress in real time:

StatusMeaning
QUEUEDUpdate queued, waiting for the device to pick it up
DOWNLOADINGDevice is downloading the changed objects
INPROGRESSDevice is installing and transitioning into the new revision
TESTINGDevice is running the new revision, performing stability checks
DONERevision committed — update successful
ERROR / WONTGOUpdate failed — the device stays on (or rolls back to) the last good revision

If the status reaches DONE, the new container is running. If it ends in ERROR or WONTGO, Pantavisor keeps the device on the previous good revision — no manual intervention needed.

Next Steps​