Skip to main content
The single_host_oss appliance installs from a release manifest instead of building runtime components from a source checkout. The manifest binds the API binary, console bundle, guest agent, rootfs images, kernel, Firecracker, jailer, migration bundle, and nullspace-host operator tool to checksums, sizes, install paths, rollback metadata, and compatibility facts.

​
Manifest

The checked-in schema and examples live in the repository:
Required component kinds:
  • api
  • console
  • guest_agent
  • rootfs
  • template
  • kernel
  • firecracker
  • jailer
  • migration_bundle
  • operator_tool
Every component records URL, SHA256, size, architecture, version, compatibility class, release-local install path, optional active compatibility path, required/optional status, and rollback metadata. The manifest also records runtime compatibility facts for Firecracker version/commit, Firecracker snapshot data format, kernel identity, rootfs and template digests, guest-agent protocol version, runtime class, and snapshot metadata format.

​
Build A Local Manifest

Prepare a release directory with the expected artifact filenames, then generate a manifest:
When --base-url is omitted, the manifest uses file:// URLs suitable for offline media. Pass --base-url https://... when publishing artifacts to an HTTP release bucket.

​
Install Or Fetch

Install the appliance from a manifest:
Fetch artifacts without re-rendering the rest of the appliance:
Artifacts install under /opt/nullspace/releases/<release-id>/; the active release symlink at /opt/nullspace/releases/current is switched atomically. Compatibility symlinks such as /opt/nullspace/nullspace-api and /opt/nullspace/artifacts/rootfs.ext4 point at the active release. Validate active artifact state:
doctor reports the active manifest id, manifest digest, installed component versions, component checksums, verification evidence, and compatibility facts.

​
Upgrade And Rollback

Validate a future release without switching:
Apply an upgrade:
The upgrade path validates the manifest, checks host and release compatibility, fetches verified artifacts, switches the active release, and runs the ingress fixture smoke unless --skip-ingress-smoke is set. Rollback switches the active release back to the previous release recorded in the upgrade state:
Database migrations are not automatically rolled back. Use a verified appliance backup when a migration must be reversed.

​
Launch Evidence

Release artifacts alone do not prove a public launch. Before making public claims for a release, run the launch gate on a supported Ubuntu x86_64 KVM host:
Use --mode owned-domain --public-hostname <domain> for the signed owned-domain preview path.