Hardwarevereisten voor MineOS: RAM, CPU, opslag en Minecraft-servers
Plan MineOS-hardware voor RAM, CPU, Minecraft-werelden, Java-servers, gelijktijdige spelers en praktische aanbevelingen voor implementatie op ZimaOS.
MineOS hardware requirements at a glance
Size MineOS from verified upstream requirements first, then add headroom for the actual workload and persistent data.
- RAM
- No universal MineOS minimum; Minecraft server memory must be sized separately
- CPU
- No universal MineOS minimum
- Storage
- Worlds, server jars, backups, profiles, and logs dominate capacity
- Runtime
- Node.js web UI plus Java Minecraft servers
- Ports
- 8443 for web UI; 25565–25570 example Minecraft range
- Best Zima starting point
- ZimaBoard 2 1664 for a small server; ZimaCube 2 Pro for heavier worlds/modpacks
From official requirements to the right setup
Start with upstream facts for MineOS, then size the workload instead of copying generic container labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Minecraft edition/version
- Player count
- Modpack/plugins
- World size
- Number of servers
- Java heap
- Backup frequency
- Server ports
Official minimum requirements
MineOS upstream documents dependencies and Docker deployment but does not publish one numerical whole-host CPU/RAM minimum because Minecraft server workload dominates.
Do not label the lightweight Node.js management UI as the hardware requirement. Size Java heap, CPU single-thread/tick needs, world storage, backups, mods, and concurrent players per Minecraft instance.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Minecraft server CPU is the real constraint. | |
| No numerical official minimum published | Allocate memory according to Minecraft instances. | |
| 8443 | HTTPS enabled in the default Compose example. | |
| 25565–25570 TCP/UDP | Expand or change per server topology. | |
| /var/games/minecraft | Contains worlds and server data. | |
| Node.js, Java, rsync/rdiff-backup and related tools | Docker image packages required runtime tools. | |
| Not required | Minecraft server workloads generally do not use GPU. |
When to upgrade your hardware
Tick lag
Heap pressure
World/backup growth
Plan hardware growth with confidence
Fast world storage
SSD reduces save/load and chunk I/O latency.
SSD/NVMeMore RAM
Directly useful for larger Java heaps and multiple servers.
Higher-RAM hostWorld backup capacity
Use larger storage for snapshots and world backups.
Multi-bay HDD/SSD poolStronger CPU
Important for modded servers, more players, and tick-heavy worlds.
Higher-throughput CPUCan it run on ZimaOS?
Install MineOS from the ZimaOS App Store
A specific public MineOS App Store page is available.
Open MineOS in the ZimaOS App Store ↗Use the official MineOS Docker definition
Upstream provides hexparrot/mineos and a Compose file with persistent world storage.
Open MineOS repository ↗Size Minecraft separately
Treat MineOS as the manager and size each Minecraft server by players, mods, Java heap, and world workload.
Review MineOS deployment ↗Zima hardware for MineOS
MineOS management overhead is small compared with the Minecraft servers it controls.
Choose by workload
Prioritize enough RAM and decent CPU; 16 GB provides safer game-server headroom.
CPU throughput and RAM become much more important.
Zima hardware should be selected for the game-server workload, not merely for whether the MineOS web UI starts.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 1664 | More containers, larger caches, and memory-heavier services | Single-app or small multi-app deployments |
|
CPU throughput is unchanged from the 832 model, so compute-heavy work can still be CPU-limited | Get Now |
| ZimaCube 2 Pro | CPU-heavier, higher-concurrency, and consolidated workloads | Game servers, repeated media scans, higher concurrency, or many demanding containers |
|
16 GB RAM can still constrain very large game or database workloads | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
How much RAM does MineOS need?
MineOS does not publish one universal host-RAM minimum; size memory for the Minecraft servers it manages.
How many CPU cores does MineOS need?
No universal official CPU minimum is published; Minecraft tick performance and server count drive CPU needs.
What data must be persistent?
The official Docker setup persists /var/games/minecraft.
What ports does MineOS use?
The example uses 8443 for the web UI and 25565–25570 for Minecraft servers.
Does MineOS need Java?
Yes. MineOS manages Java-based Minecraft servers and the official image includes Java runtimes.
Can ZimaBoard 2 832 run MineOS?
The UI can, but 8 GB RAM leaves less headroom for Minecraft; the 16 GB model is a safer practical starting point.
Does MineOS need a GPU?
No.
When should I choose ZimaCube 2 Pro?
For modded servers, more players, multiple instances, or tick-heavy worlds.
