Lucky Hardware Requirements: RAM, CPU, Storage & Network Services
Plan Lucky hardware for RAM, CPU, DDNS, reverse proxy, port forwarding, WebDAV, Docker networking, and practical ZimaOS deployment.
Lucky hardware requirements at a glance
Size Lucky from verified upstream requirements first, then add headroom for the actual workload and persistent data.
- RAM
- No numerical official minimum published
- CPU
- No numerical official minimum published
- Storage
- Small app footprint plus configuration and logs
- Networking
- Host network mode is recommended on Linux
- Docker
- Official image: gdy666/lucky:v2
- Best Zima starting point
- ZimaBoard 2 832
From official requirements to the right setup
Start with upstream facts for Lucky, 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
- Enabled modules
- Reverse-proxy traffic
- TLS/ACME use
- Port-forward rules
- WebDAV/FTP traffic
- IPv4/IPv6 needs
- Host networking
- Config backups
Official minimum requirements
Upstream documents installation and runtime behavior but does not publish a numerical whole-host CPU, RAM, or disk minimum.
Do not treat app-store memory metadata as an upstream official minimum. Lucky is intentionally lightweight; real sizing depends on which network and file-service modules are enabled.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Depends on proxy, TLS, file-service, and rule volume. | |
| No numerical official minimum published | Designed to run on resource-constrained Linux devices. | |
| gdy666/lucky:v2 | Current Docker path uses the Wanji feature set. | |
| 16601 | Verify conflicts before exposing. | |
| Host mode on Linux | Recommended for IPv4/IPv6 behavior. | |
| /app/conf for current v2.23.1+ image | Persist configuration outside the container. | |
| Not required | No GPU workload. |
When to upgrade your hardware
Proxy/TLS load
File-service traffic
Host consolidation
Plan hardware growth with confidence
Persistent config
Keep Lucky configuration on durable SSD-backed storage.
SSD/persistent volumeMore RAM
Useful mainly when Lucky shares the host with many other apps.
Higher-RAM hostFaster network
Helps heavy proxy, WebDAV, or file-transfer workloads.
2.5GbE/10GbE when justifiedStronger CPU
Useful for sustained TLS/reverse-proxy load.
Higher-throughput CPUCan it run on ZimaOS?
Install Lucky from the ZimaOS App Store
A specific public Lucky App Store page is available.
Open Lucky in the ZimaOS App Store ↗Use the official Lucky deployment guidance
Upstream documents Docker, host networking, and persistent configuration.
Open Lucky installation docs ↗Preserve network behavior
Check host-mode networking and port ownership before combining Lucky with other proxies or file services.
Review Lucky networking guidance ↗Zima hardware for Lucky
Lucky itself is light; network traffic and enabled modules usually determine scaling.
Choose by workload
A low-power ZimaBoard is sufficient.
Network throughput and CPU become more important.
Zima recommendations are practical mappings, not upstream-certified hardware tiers.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light self-hosted services and small home-server workloads | Single-app or small multi-app deployments |
|
8 GB RAM and the 4-core N150 can constrain heavier game servers, large scans, and multi-service consolidation | Get Now |
| 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 Lucky need?
Upstream does not publish a numerical whole-host RAM minimum.
How many CPU cores does Lucky need?
No official numerical CPU minimum is published.
Which Docker image does Lucky use?
The official Docker documentation uses gdy666/lucky:v2.
What port does Lucky use by default?
The default management port is 16601.
Why is host networking recommended?
Lucky's Linux Docker guidance recommends host mode for full IPv4/IPv6 behavior.
Can ZimaBoard 2 832 run Lucky?
Yes for typical DDNS, port forwarding, ACME, and light reverse-proxy workloads.
Does Lucky need a GPU?
No.
When should I choose ZimaCube 2 Pro?
For sustained proxy/TLS load, heavier file services, or wider host consolidation.
![Unifi-controller [legacy]](http://shop.zimaspace.com/cdn/shop/files/Unifi-controller_legacy.webp?v=1790688426&width=1000)
