System Requirements
TrixOS has two kinds of hosts: one panel (the control server) and one site agent per datacenter whose servers you want to install over PXE. A small setup can run the panel inside the datacenter network and skip the agent; see Site Agents.
| Minimum | Recommended | |
|---|---|---|
| CPU | 2 vCPU, x86_64 | 4 vCPU |
| Memory | 2 GB | 4 to 8 GB |
| Disk | 40 GB | 100 GB or more if you keep custom ISOs and many boot images |
| Operating system | Ubuntu 22.04 or 24.04, Debian 12 or 13 | a fresh server used only for TrixOS |
| Software | Docker Engine with the Compose plugin (the install script installs it) |
The panel runs as a set of containers: api, worker, poller, assets (boot-file cache), viewer
(console launcher), web, postgres and redis. Postgres and Redis are part of the Compose file; you don’t
need to install them yourself.
Disk use grows with:
- Boot files. Kernels, initrds and live images are downloaded once and cached. Live systems such as SystemRescue or Clonezilla are several hundred megabytes each.
- Custom ISOs you add to the OS catalogue.
- History. Bandwidth samples are kept for 400 days, sensor samples for 90 days.
Network
Section titled “Network”- Inbound: HTTPS for the web UI and API. Put a reverse proxy with TLS in front of the panel (it listens on port 8088 by default). The site agents connect over WireGuard (UDP 51820) and HTTPS.
- Outbound: HTTPS to the license server (
license.trixos.sh), to OS mirrors (for exampledeb.debian.org, Rocky, Alma and Ubuntu mirrors) and to the download sites of the live systems you use. - BMCs: the panel must reach every BMC on IPMI (UDP 623) or HTTPS (Redfish). Usually it does that through the site agent’s WireGuard tunnel.
Site agent
Section titled “Site agent”| Requirement | |
|---|---|
| Host | Small VM or physical host, 1 vCPU, 1 GB memory, 10 GB disk |
| Operating system | Debian or Ubuntu with Python 3 |
| Interfaces | One interface in the network your servers PXE-boot from, one in the out-of-band (BMC) network |
| Network | Reaches the panel over HTTPS; WireGuard (UDP 51820) between agent and panel |
The installer adds what the agent needs: wireguard-tools, nftables, dnsmasq-base, ipxe, nginx and curl.
The agent answers DHCP only for servers with a running install job, so it can share a network with another
DHCP server as long as that one does not answer the same servers at the same time.
Servers and BMCs
Section titled “Servers and BMCs”- A BMC with IPMI over LAN (
lanplus) or Redfish. Vendor-specific handling exists for HPE iLO, Dell iDRAC, Lenovo XClarity and Supermicro. - For OS installs and rescue: network boot (PXE) enabled on the NIC that is connected to the provisioning network, in legacy BIOS or UEFI mode.
- At least one public IPv4 address assigned in TrixOS. PXE jobs are refused without one, because the installed system needs it.
Browser
Section titled “Browser”Any current version of Firefox, Chrome, Edge or Safari. The graphical console uses noVNC in the browser; no Java or plug-ins are needed on your computer.