Navigation
ELOWEN · Documentation

Last updated: October 27, 2026

Browse documentation · Prepare a host for managed environments
Operations and updates

Prepare a host for managed environments

Get the machine that runs Chetty ready so managed Projects can create their first environment.

Before you start

Only administrators can prepare a host. Preparation runs once, and later environments reuse it.

Check the host

  1. Open Settings → Plugins → Environments.
  2. Open Host and read the Machine environment panel.
  3. Read every area: Container tools, System services, Privileged boundary, Machine access policy, Network isolation, Published root filesystems and Existing environments. Each requirement shows Ready or Missing.

The panel reports one of three states: Ready for new environments, Ready and cached locally or Preparation required.

Prepare the host

  1. Select Prepare host.
  2. Follow Preparation progress through Preparing host services, Caching the root filesystem and Checking readiness.
  3. Try the first start again once the panel reports Ready for new environments.

What preparation sets up

Area What it provides
Container tools Operating-system packages required to launch systemd machines.
System services Root-owned unit templates and services that start and supervise machines.
Privileged boundary The fixed helper contract and host compatibility checks.
Machine access policy The narrow policy used for machine lifecycle operations.
Network isolation Forwarding, link configuration and fixed isolation rules for private machine links.
Published root filesystems Pinned archives this release can verify and materialize. Missing local copies are downloaded during preparation or first use.
Existing environments Compatibility state of environment records already stored on this instance.

Root filesystems

The host retrieves and verifies a published root filesystem when it is needed. Creating an environment requires a prepared host and an available, verifiable root filesystem, so the first start is refused when a requirement is missing.

Older environments

Environments and snapshots left from the removed Podman runtime cannot be started or restored. They can be deleted individually or with their Project; delete the Project and create it again to get a working environment.

Check that it worked

The panel reports Ready for new environments, and the Project's first Start environment finishes instead of being refused.

If it does not work

  • A requirement stays missing: retry Prepare host and read Preparation progress. A failed step names what it needs.
  • A root filesystem cannot be downloaded: check the host's network access, then prepare the host again.
  • Disk figures are missing or a disk limit is refused: the sandbox data directory must be on a disk or partition the host can account for.

Continue with Start, stop and snapshot an environment, Set environment limits and networking or Environments overview.