Skip to main content
Version: 029-rc4

Remove applications

Removing an application follows the same revision workflow as adding one: remove the container from your local pvr checkout, commit, and deploy. Pantavisor stops the container and removes it from the trail on the next boot.

Step 1 — Clone the Device State​

If you do not already have a local checkout, clone the device:

pvr clone http://<device-ip>:12368/cgi-bin my-device
cd my-device

The directory mirrors the device's current revision:

my-device/
├── bsp/
├── network/
├── sensor-app/
├── my-old-app/           ← the container you want to remove
├── _config/
├── device.json
└── _sigs/

Step 2 — Remove the Container​

Use pvr app rm to remove the container from the local state:

pvr app rm my-old-app

This deletes the container's directory from your checkout.

Step 3 — Commit and Deploy​

Then stage and commit the removal, and deploy to the device:

pvr add .
pvr commit -m "remove my-old-app"
pvr post http://<device-ip>:12368

Step 4 — What Happens on the Device​

Pantavisor installs the new revision, then transitions into it — stopping and discarding the removed container. A reboot happens only if a system restart-policy container (or the BSP) changed.

After the transition, pvcontrol container ls and lxc-ls -f will no longer show the removed container. The previous revision (with the container) is kept in the trail: to restore it, roll back by running that revision on the device (pvcontrol cmd run <revision>), or redeploy it from Pantahub's revision history.