Cosmos Hardware Requirements: RAM, CPU, Storage & Reverse Proxy & Container Management
Plan Cosmos hardware for RAM, CPU, reverse proxying, container management, VPN, Docker socket access, and practical Zima-host deployment recommendations.
Cosmos hardware requirements at a glance
Size Cosmos from verified upstream requirements first, then add headroom for workload and persistent data.
- RAM
- No numerical official minimum published
- CPU
- No numerical official minimum published
- Storage
- Persistent /var/lib/cosmos plus managed app data
- Networking
- Host network strongly recommended on Linux
- Privileges
- Docker socket access required; privileged mode or capabilities may be required
- Best Zima path
- Not recommended as a normal ZimaOS app-store stack
From official requirements to the right setup
Start with current upstream facts for Cosmos, then size the real workload rather than copying generic container or app-store labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Ports 80/443
- Docker socket access
- Host network
- Managed container count
- Constellation VPN
- Persistent config
- Reverse-proxy role
- Conflict with ZimaOS app orchestration
Official minimum requirements
Cosmos publishes explicit installation topology and privilege/network requirements but no numerical whole-host CPU, RAM, or disk minimum.
The project explicitly warns not to install Cosmos through CasaOS or Portainer stacks and recommends direct Docker execution with host networking. That warning must be preserved in ZimaOS guidance.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Reverse proxy/VPN/management load varies. | |
| No numerical official minimum published | Depends on managed services and host load. | |
| azukaar/cosmos-server:latest | Used in the documented install command. | |
| Host network recommended on Linux | Cosmos is designed to bind 80/443 directly. | |
| 4242/udp | Used by Constellation. | |
| /var/run/docker.sock mount required | Needed to manage containers. | |
| Not required | No GPU workload. |
When to upgrade your hardware
Managed apps increase
Proxy/VPN load
Port/orchestration conflict
Plan hardware growth with confidence
Persistent config
Keep /var/lib/cosmos on reliable storage.
SSDMore RAM
Size for the applications Cosmos manages, not just Cosmos.
Higher-RAM hostFaster network
Useful for reverse proxy and VPN throughput.
2.5GbE/10GbEIsolation
Use a dedicated VM/host to avoid control-plane conflicts.
Dedicated VM/hostCan it run on ZimaOS?
Do not install Cosmos as a normal ZimaOS App Store stack
The upstream project explicitly warns against CasaOS/Portainer stack installation and expects direct host-level Docker access.
Custom install Cosmos in the ZimaOS app ↗Prefer a dedicated VM or separate host
This avoids Docker-socket, host-network, port 80/443, and orchestration conflicts with ZimaOS.
Open Cosmos installation instructions ↗Preserve host networking and Docker access
If used, follow the direct Docker command and understand the security implications of privileged/docker-socket access.
Review Cosmos installation command ↗Zima hardware for Cosmos
Cosmos is a host-level management platform rather than an ordinary application container; it competes with ZimaOS for reverse-proxy and container-control responsibilities.
Choose by workload
Use a separate VM or disposable host rather than a normal ZimaOS app slot.
Size hardware for all managed apps plus proxy/VPN traffic.
Do not recommend running Cosmos casually inside ZimaOS without isolating these control-plane conflicts.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaCube 2 Pro | CPU-heavier, database-heavier, and higher-concurrency services | Larger production-style self-hosted workloads |
|
16 GB RAM can still be low for larger enterprise monitoring/search/control-plane deployments | 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
Does Cosmos publish a RAM minimum?
No numerical whole-host RAM minimum is published.
Which Docker image is used?
azukaar/cosmos-server:latest.
Which ports does Cosmos expect?
80 and 443 for reverse proxying, plus 4242/udp for Constellation VPN.
Does Cosmos need Docker socket access?
Yes, the official command mounts /var/run/docker.sock.
Can I install Cosmos through CasaOS or Portainer Stack?
The upstream project explicitly says not to do that.
Can I run Cosmos as a normal ZimaOS app?
That is not recommended because of orchestration, host-network, Docker-socket, and port conflicts.
Does Cosmos need a GPU?
No.
What is the safer topology?
A dedicated VM or separate host.
