Supported platforms
The distributions and architectures Maran installs on, and the floors the installer enforces before it changes anything.
Distributions
| Family | Versions |
|---|---|
| Ubuntu | 22.04 · 24.04 · 26.04 LTS |
| Debian | 12 · 13 |
| AlmaLinux | 8 · 9 · 10 |
| Rocky Linux | 8 · 9 · 10 |
| Red Hat Enterprise Linux | 8 · 9 · 10 |
| Oracle Linux | 8 · 9 · 10 |
Architectures: x86_64 and aarch64.
Both are built against glibc 2.28. The firewall step is not yet verified end to end on ARM64 hardware.
The four enterprise rebuilds each get their own row because each reports its own ID in
/etc/os-release, and the installer matches on that instead of guessing from ID_LIKE. Once
matched, they all run the same code path. The fallback only decides which package manager to use.
The list above decides whether a distribution and version were ever meant to be admitted, and
mixing the two up is how an untested target gets in.
AlmaLinux 8 is the oldest supported release. Its glibc 2.28 is the oldest the agent is built against. CentOS 7 is absent because it cannot run the panel at all: glibc 2.17 is below what a self-contained .NET 9 publish needs.
A distribution outside this table is not supported. The installer knows each supported family's package layout and service names, and it refuses to guess at any other.
What the installer requires
The preflight step enforces two hard minimums before anything on the server changes:
- 1024 MB of RAM;
- 2048 MB of disk for Maran's own files.
These are minimums, not recommendations. A server that hosts real sites needs considerably more. Free space on the backup filesystem below 10240 MB produces a warning, not a refusal.
Preflight collects every failure before it exits, so a server with three problems reports all three at once.
Production installs are native
There is no container in a production install. The panel, the agent, PostgreSQL and the hosting stack are installed as ordinary system services. Docker is used in development only.