Skip to content

Voxeltron 0.1.2

Choose a tag to compare

@jaikoo jaikoo released this 15 Nov 10:25
· 2 commits to main since this release
51f9416

0.1.2 is the first release after 0.1.0. A 0.1.1 was built and signed but
never published; everything planned for it is in 0.1.2, together with the
fixes from the second round of battle testing.

Added

  • Crashed apps deployed with vxl deploy are restarted automatically, up to [lifecycle.remediation] max_restarts (3) times in window_secs (600) with backoff, then quarantined with one crash_quarantine alert. Before, they raised crash_detected and stayed down. The limits and [lifecycle] healthy_window_secs (120) are configurable.
  • Approval-gated self-healing, off by default ([self_healing] enabled = true). A quarantined crash loop becomes a proposal to roll back to the previous deployment; the request goes to your [monitoring.channels], vxl approvals list|approve|deny decides it, the daemon checks the app recovered (remediation_recovered or remediation_failed), and a denial leaves the app quarantined (remediation_denied). Needs gRPC auth and security.operator_admins. See "Crash recovery and self-healing" in docs/self-hosting.md.
  • vxl audit export prints the daemon audit trail. Runbook approvals now record the approver's token subject.

Upgrade notes

  • After upgrading from 0.1.0, run sudo vxl-admin node harden (or rerun the installer). Databases created on 0.1.0 are not adopted: recreate them.
  • systemctl restart nftables flushes the whole ruleset, including Docker's own firewall chains. Voxeltron's metadata egress table is reapplied automatically. Run sudo systemctl restart docker afterwards to restore Docker's chains; until then vxl-admin doctor audit reports HARDEN-FW-001.
  • On a host whose default routes use several interfaces, run sudo vxl-admin node harden --public-interface <name>.
  • Hosts without nftables print "metadata egress block NOT installed: nftables missing". Install nftables, then run sudo vxl-admin node harden.
  • ops/upgrade.sh refuses hosts where nft -f fails, such as unprivileged LXC containers.
  • The first daemon start after the upgrade recreates each managed Redis database's container so it requires its password (managed Redis now requires its password in the log). Apps that connected without the password must use REDIS_URL or REDIS_PASSWORD.
  • Hosts installed with 0.1.0 use Docker's default address pools, which run out at about 15 apps. Rerun the installer, or add default-address-pools to /etc/docker/daemon.json as docs/self-hosting.md shows, then sudo systemctl restart docker.

Security

  • Alerts from the built-in rules are readable on every edition, in the TUI and by the agent. Custom alert rules remain a Team and Enterprise feature.
  • Each agent tool call in the audit log names its conversation (session_id) and whether it came from the agent or a direct tool call. Calls refused by the permission ceiling or an entitlement are audited as denied.
  • The release signing key was rotated on 1 Nov 2026. Releases are now signed with minisign key ID AE5B254F98D5E1CA (public key RWTK4dWYTyVbrgcV0LOIXqg6p6RQECLoyMXoLGZt6e9NcOzW33vpwu7+, also at https://voxeltron.dev/release-key.txt). Do not trust anything signed by the previous key, including the 0.1.0 SHA256SUMS.minisig. The site installer, ops/upgrade.sh and scripts/install.sh trust only the new key.
  • HSTS is not sent. An opt-in per-app Strict-Transport-Security setting is planned for 0.1.2.
  • Apps with a domain are served over HTTPS only. Plain HTTP now redirects to HTTPS; before, Caddy's server listened on port 80 as well and served every app in clear text with no redirect. Existing hosts move over when the daemon starts. If your own Caddyfile puts the server that serves Voxeltron apps on port 80, the daemon logs an error at startup and vxl-admin doctor audit fails HARDEN-EDGE-001.
  • The assistant's http_request tool (POST, PUT, DELETE and PATCH) is off by default. It exists only when ai.http_request.allowed_hosts lists hosts, sends only to them, never follows a redirect, caps request bodies at 64 KiB, and refuses Cookie, forwarding and method-override headers. HTTP tools read at most 100 KiB of a response. Calls are audited with method, host, path (long segments hashed), status and sizes. There is no per-call approval, so list only hosts the assistant may change.
  • The assistant's verifier and anomaly diagnosis no longer exceed the operator's ai.max_permission. Before, with the default read ceiling they could still run Safe-tier tools such as restarting or stopping a container. Verification is now capped at the lower of the configured ceiling and Safe, and anomaly diagnosis is strictly read-only.
  • Assistant tool calls refused for exceeding the permission ceiling or for a missing entitlement are now written to the audit log with outcome denied, the caller, the tool and the reason. Parameters are never recorded.
  • SOPS and Infisical project reads no longer return global values. A SOPS project read now returns only projects.<name>.<key>; if you relied on flat top-level keys being served to projects, move them under projects.<name>. Infisical serves global secrets only until per-project mapping exists.
  • Compose ${vault:KEY} references resolve only secrets from the project (or the scope the reference names). A project reference no longer falls back to a global secret of the same name.
  • Credentials in Git URLs are redacted from logs and error messages.
  • Installing a plugin is limited to operator admins, and plugin names must be lowercase letters, digits and hyphens (up to 64 characters, starting with a letter or digit). Plugins remain off by default.
  • Log queries return at most 1000 entries per page.
  • Managed Redis databases created with vxl db create require their password. Before, Redis ran without one although apps were given REDIS_PASSWORD and a REDIS_URL with it, so any container on the project network could read and write it. The password reaches Redis through the container environment and a 0600 file on the container's tmpfs, never through an argument list. Existing Redis databases are recreated on the same volume, with their data, when the upgraded daemon starts.

Fixed

  • The assistant's get_project_status reported a crash-looping app as "Creating". It now reports health as vxl status does, with the current deployment, its container and any quarantine.
  • voxeltrond config validate refuses [ai] provider without model. No provider has a default model; before, every call failed at runtime with an empty model name. The DeepSeek models are now deepseek-flash and deepseek-v4-pro.
  • The installers wait up to 45 minutes (was 10) for the package lock that unattended-upgrades holds on a new server, say once a minute which process holds it, and stop with what to do if it stays held. APT_LOCK_TIMEOUT accepts up to 7200 seconds.
  • The assistant's log lines are scrubbed the same way from every source (URLs, secrets, one line each, at most 2,000 characters) and are marked as untrusted app output. Tools the edition does not include are no longer offered to the assistant.
  • The operations agent can find apps by name (list_apps, and app names in get_project_status, list_deployments, query_logs and query_metrics). Before, it needed project UUIDs it had no way to discover.
  • query_logs reads the app's container logs, with the app's secrets and personal data masked. Before, without Loki, it always returned nothing.
  • query_metrics finds an app's CPU, memory, restarts and health by app name, and says when a metric is not collected instead of returning an empty result. Restart counts are now recorded, so the built-in restart-loop runbook can detect a restart loop.
  • The agent keeps its own tool results between steps and never sends the same successful mutating request twice in a run. Before, with providers that return no text alongside a tool call (such as DeepSeek), it lost its results and could repeat a POST.
  • investigate_incident, analyze_logs, correlate_events and suggest_fix use the configured AI provider. Before, they always failed with "no AI provider configured".
  • A failed vxl up is recorded: vxl status and the agent show the failure and its fix (for example VXL-FS-001). Log evidence still stays with the CLI.
  • Apps deployed with vxl up keep their deployment record across a daemon restart, including when the deploy request was interrupted. Before, they could stay pending forever.
  • ai.http_request.allowed_hosts explains a host:port entry correctly, and accepts a bare IPv6 address.
  • Apps with a managed database, and apps deployed with vxl deploy, come back after a host reboot.
  • Rerunning the installer to upgrade restarts the daemon onto the new binary.
  • vxl-admin update and ops/upgrade.sh keep the daemon executable by its service user.
  • vxl daemon upgrade --verify-runtime-compat works on Docker installs. Releases now publish a signed release-manifest.json.
  • vxl bootstrap and vxl daemon upgrade work as a passwordless-sudo user, on Linux arm64, and when a prerequisite package must be installed.
  • A second app with a domain deploys (Caddy TLS policies are updated in place).
  • vxl deploy takes --git-commit or --git-tag for git sources.
  • vxl secrets and vxl compose accept project names. Permission errors show the daemon's reason.
  • vxl rollback works for apps deployed with vxl up.
  • The 14-day certificate expiry alert no longer fires for certificates from Caddy's local CA (tls internal), which last about 12 hours and renew themselves.
  • A crash alert for an app the kernel killed for running out of memory says so, instead of only "exit code 137".
  • More than about 15 apps on one host. Docker's default address pools allow about 31 networks, and Voxeltron uses one per project and one per deployment; past that, deploys and reboot restores failed. The installers now give Docker /24 pools (4096 networks) when /etc/docker/daemon.json does not exist, and print the setting to add when it does.
  • Managed Redis keeps its data across a reboot or restart. Stopping it now writes a final snapshot (the container could not forward the stop signal, so every stop was a hard kill), and it snapshots within a minute of a write. Before, writes since the last hourly snapshot were lost.
  • vxl up waits for the manifest's health: path before the new version takes traffic. Before, the path was ignored.
  • Redeploying with vxl deploy keeps one previous deployment as the rollback standby and stops older ones. Before, every earlier generation kept running, and all of them came back after a reboot.

Verify

shasum -a 256 -c SHA256SUMS
minisign -V -P RWTK4dWYTyVbrgcV0LOIXqg6p6RQECLoyMXoLGZt6e9NcOzW33vpwu7+ -m SHA256SUMS -x SHA256SUMS.minisig

The trusted comment must read voxeltron v0.1.2.

Third-party notice. The Linux voxeltrond and vxl-admin include BusyBox, under the GNU General Public License, version 2 only. Its complete source is attached to this release (busybox_1.36.1-6ubuntu3.1.dsc and its files, with BUSYBOX-SOURCE-README.md); the licence and written offer are in NOTICE-busybox.md.