Overview
Every ALYPOD CPU Pod is deployed from an operating-system image. The ALYPOD Console offers a range of current Linux distributions and Windows Server, and you can reinstall a different image at any time from the Pod detail page.
Available images
Linux
- Ubuntu 22.04 LTS and 24.04 LTS
- Debian 11 and 12
- AlmaLinux 8 and 9
- Rocky Linux 8 and 9
- Fedora (current release)
- Alpine Linux
- Arch Linux
Windows
- Windows Server 2019 and 2022 (available on Windows Pods)
Application images
Some locations also offer pre-built images such as a LAMP stack or Docker host. These are convenience images; you can achieve the same result by installing packages yourself.
Choosing an image
- For long-term servers, pick an LTS release (Ubuntu LTS, Debian, AlmaLinux, Rocky) for a stable, supported base.
- For the newest kernels and packages, choose Fedora or Arch — but expect more frequent upgrades.
- For lightweight containers or very small Pods, Alpine uses far less disk and RAM.
- For .NET, MSSQL or RDP access, choose Windows Server on a Windows Pod.
Reinstalling
- Open the Pod in the ALYPOD Console.
- Click Reinstall, choose the new image and your SSH key.
- Confirm. Reinstalling erases all data on the Pod, so snapshot first.
Troubleshooting
- Problem: Architecture mismatch when installing a package. Solution: Check with
uname -m; ARM Pods reportaarch64and need Arm-compatible builds. - Problem: Windows image not listed. Solution: Windows requires a Windows Pod plan; Linux and Windows images are not interchangeable.
Related articles
- [Deploying your first Pod]
- [Choosing the right CPU Pod for your workload]
- [Understanding your ALYPOD dashboard]
