Pantavisor 031 is out.
The highlights:
- cgroup v2 support. Pantavisor can now run containers on cgroup v2, the interface current Linux distributions use, as well as on cgroup v1. It picks the version from
PV_SYSTEM_CGROUP_VERSION(1,2orauto). Containers without cgroup settings need no changes. - LXC 6 by default, LXC 7 to try. LXC 6 is now the default runtime, and LXC 7 is available; it runs on cgroup v2 only.
- A wider TLS trust pool. Devices trust the root certificates of the six largest public CAs, not only Let’s Encrypt, so they can reach far more HTTPS servers. A new denylist lets a BSP update block a certificate.
- Device identity reset. A device can get a new Pantacor Hub identity without being re-flashed.
- STAGED containers. A container can be fully set up at boot and started only when you ask for it. This is the groundwork for D-Bus auto-activation, where Pantavisor starts a service the first time something calls it.
- Quieter logs, and revisions written for newer Pantavisor versions still install on 031.
- In the layer: dm-verity for container volumes, one SDK in place of the per-board SDKs, and a Jetson Nano port with CUDA.
Images are published for 14 machines, from Raspberry Pi, Rockchip and Allwinner boards to i.MX8 and Docker.
Before you upgrade
- User metadata can set fewer config keys. Hub user metadata can no longer set 19 keys that could make a device unreachable or unsafe. Among them are the updater intervals and timeouts,
PV_DEBUG_SSH_AUTHORIZED_KEYS, the storage GC thresholds,PV_REVISION_RETRIESand thePV_POWER_*keys. A key that is not allowed is ignored and the log shows a warning. Set these keys inpantavisor.configor the OEM config instead. The configuration reference lists the levels each key accepts. - Numeric log levels moved up by one. The new
WALLlevel sits just beforeINFO, soINFO,DEBUGandTRACEare now 4, 5 and 6. If you setPV_LOG_LEVELas a number, check it. - LXC 6 is the default runtime. Builds that did not pick an LXC version move from LXC 3 to LXC 6 on their own. To stay on LXC 3, add
PANTAVISOR_FEATURES:append = " lxc-deprecated".
What’s new in Pantavisor itself
TLS: a wider trust pool, and a denylist
-
Devices used to trust only one certificate authority, Let’s Encrypt, so they could reach Pantacor Hub but few other HTTPS servers. Now they trust the root certificates of the six largest public CAs: Let’s Encrypt, DigiCert, Sectigo, GlobalSign, Google Trust Services and Amazon, 25 roots taken from the Mozilla bundle. No action is needed: they are in every 031 image. To see them on a device:
ls /etc/thttp/certsTo add a root in your build, name its file from the Mozilla bundle (in
/usr/share/ca-certificates/mozilla/, without.crt):PV_TLS_CA_CERTS:append = " Microsoft_RSA_Root_Certificate_Authority_2017"The community post lists every root and its limits.
-
New certificate denylist: a file of SHA-256 hashes of certificate public keys. Pantavisor refuses any chain that contains one of them, whether it is the server certificate, an intermediate or a root. This works without a reliable clock. The file is
/etc/thttp/denylistby default; setPV_LIBTHTTP_DENYLISTto use another path. A missing file means no denylist. To get the hash of a certificate:openssl x509 -in cert.pem -pubkey -noout | openssl pkey -pubin -outform DER | sha256sum | cut -d' ' -f1See Certificate Denylist.
Device identity reset
A device can get a new Pantacor Hub identity without being re-flashed. Use it to hand a device to a new owner or to replace credentials that may have leaked. Pantavisor removes the old credentials and cleans out the old revisions. The device then registers as a new device, linked to the old one, and waits to be claimed.
-
From the Hub: Lock identity, then Rotate identity, on the device’s page.
-
From the device, on a DONE local revision:
pvcontrol cmd reset-identity
This also works with PV_CONTROL_REMOTE_ALWAYS=0. Walkthrough: Device identity reset.
STAGED: containers that wait to be started
A STAGED container is fully set up at boot, with its volumes mounted and drivers loaded, but its process is not started. Boot does not wait for it. You start it when you need it:
{ "PV_LIFECYCLE_GOAL": "STAGED", "PV_STATUS_GOAL": "STARTED" }
pvcontrol containers start my-app
STAGED goes in the new lifecycle_goal field. A Pantavisor older than 031 ignores that field and uses status_goal instead, so a revision that brings 031 and a STAGED container in the same update still installs. To start a STAGED container this way, it needs restart_policy: "container". pvr 055 supports it (pvr app add --lifecycle-goal STAGED). Details: New container goal STAGED.
In 031 you start a STAGED container yourself. Its main purpose comes next: D-Bus auto-activation on the system bus that Pantavisor hosts for containers. A service such as pv-avahi waits in STAGED, and Pantavisor starts it the first time another container calls its bus name. Nothing runs until it is needed, and the start is quick because the container is already set up. This work is in review and is not part of 031 (pantavisor#738, pantavisor#820). STAGED is useful today for software you need only now and then, such as diagnostics or provisioning tools.
cgroup v2
-
New setting
PV_SYSTEM_CGROUP_VERSION:1,2orauto. Pantavisor sets up cgroups to match. Before a container starts, it removes the LXC cgroup lines that belong to the other cgroup version. -
The device reports which cgroup layout and version it uses in its device metadata, as
pantavisor.cgroup.layoutandpantavisor.cgroup.version:pvcontrol devmeta ls -
Most containers need no changes. If yours set device lists or limits, follow cgroup v2 support and how to migrate.
Logging
- New
WALLlog level. Container status changes are logged at it, andWALL,ERRORandFATALmessages are always shown on the console, even whenPV_LOG_LEVELkeeps them out of the logs. - Each container gets its own
/dev/logsocket. It replaces the old symlink, so standardsyslog()messages are reliably captured and attributed to the right container. - Log files are no longer synced to disk after every write. How often they are synced is set with
PV_LOG_SYNC(defaultsmart) andPV_LOG_SYNC_BOOT_WINDOW. PV_LOG_CAPTURE,PV_LOG_SERVER_OUTPUTSandPV_LOG_CAPTURE_DMESGset in a revision’s OEM config now take effect.PV_LOG_CAPTURE=0now really stores nothing.- Routine Hub polling, control-API requests, controller and wakelock messages moved to
TRACE. In their place there is a shortINFOheartbeat every 10 minutes (PV_LOG_HEARTBEAT_INTERVAL) and aDEBUGsummary of Hub requests every minute (PH_LOG_SUMMARY_INTERVAL). - Fixed: the size of rotated logs, the format of truncation messages, and the log upload position after a restart.
Faster, and quieter on the network
- Registering, claiming and syncing with the Hub no longer block Pantavisor’s main event loop.
- xconnect checks its links less often when nothing changes, and logs less while doing so.
Forward-compatible parsing
- An unknown enum value now logs a warning and falls back to a default instead of rejecting the revision. Unknown disk and pool types are skipped. Key lookups now match the whole key name, not just its beginning.
- The rule is now written down: newer revisions must still install on an older Pantavisor.
Smaller fixes
- With dm-verity, Pantavisor no longer skips checksum checks on a volume’s data unless the dm-verity mount handler actually runs. Before, such volumes could end up neither checksummed nor verified.
- The user metadata value of a config key is no longer saved into
pantahub.config. pvtxpads tar metadata to a full 512-byte header block.- The
.pvfolder is no longer listed as a revision. /runis mounted with mode 0755.- The mdev mount hook no longer writes debug output to syslog.
Full list: pantavisor 031 release and all changes since 030.
Highlights across the layer
LXC 6 by default, LXC 7 to try
-
lxc-stable(LXC 6) is the default.lxc-next(LXC 7, cgroup v2 only) is new.lxc-deprecated(LXC 3) is still available. -
The default
PV_SYSTEM_CGROUP_VERSIONfollows the LXC version:autofor LXC 6,2for LXC 7,1for LXC 3. A build that asks for cgroup v2 stops with an error if the kernel lacksCONFIG_BPF_SYSCALLorCONFIG_CGROUP_BPF. -
The reference images:
rpiuses LXC 7 with cgroup v2, the Orange Pi 3 LTS uses LXC 3, and every other board uses LXC 6. To try LXC 7 yourself:./kas-container build kas/build-configs/release/docker-x86_64-scarthgap.yaml:kas/with-lxc-next.yaml
dm-verity for container volumes
- Set
PVR_DM_VERITYin a recipe that usescontainer-pvrexportto protect its volumes with dm-verity. Pantavisor then mounts them through dm-verity.pv-example-verityis an example container.
One Pantavisor SDK
- It replaces the per-board SDKs, with installers for armv6, armv8 and x86_64.
- It adds LVGL, WPE WebKit with cog, GPIO, camera and video packages, and other libraries for embedded apps.
- The installers are on the release page and listed in
releases.json.
Jetson Nano (build from source)
- meta-tegra port with CUDA, core containers, drivers, and firmware for the Intel 8265 Wi-Fi and Bluetooth.
pv-unslothadds a CUDA gateway and a chat page. - There are no 031 images for it yet. Build it with
kas/build-configs/jetson-nano-kirkstone.yaml. The Jetson Nano port guide has the details.
Images, signing and connectivity
- The
pv-trustclass builds images signed with your own signing identity. libthttpships the 25 root certificates of the trust pool. The list isPV_TLS_CA_CERTSinrecipes-pv/libthttp/libthttp_git.bb.pantavisor-image-baseholds the generic parts of a flashable image, with auboot-gptlayout for U-Boot boards.- The Orange Pi i96 is now a release machine, with a flashable wic image.
- New
pv-mqtt-sdkcontainer, which connects a device to Pantacor Hub over MQTT. pvwificonnect1.13.0 can run as a mgmt container and can be built with a preset Wi-Fi network.- BSPs now record their build metadata in
bsp/build.jsonandbsp/src.json.
Notable fixes
- Rockchip saves its try-boot state, so a failed revision rolls back.
u-bootsavespv.envwith an absolute path on ext4 boot partitions.pv-avahistartsavahi-daemonagain when it loses the race for its D-Bus name.- On Variscite boards, Wi-Fi and OpenThread are now turned on at first boot instead of during the build.
Component updates: pantavisor 48c5823 → 604d180, libthttp (certificate denylist), dropbear 2026.94, LXC 6 fork update, new LXC 7 fork, pvr 055, Go 1.26.10 (pvgo), pv-tailscale v1.96.5, pv-mqtt-sdk v0.1.13, pvwificonnect v1.13.0, pv-alpine-connman 1.3.7.
Get 031
The 031 release page has images, PV exports and BSPs for every machine, plus SDK installers for each architecture. Each download is listed with its checksum. Full notes are in CHANGELOG/CHANGELOG-031.md.
To build it yourself:
git clone https://github.com/pantavisor/meta-pantavisor && cd meta-pantavisor
git checkout 031
./kas-container build kas/build-configs/release/docker-x86_64-scarthgap.yaml
Docs are at docs.pantavisor.io. Tell us here what works, what breaks, and which boards you want next.