Configuration matérielle requise pour OpenList : RAM, processeur, stockage et systèmes de stockage pris en charge
Planifiez le matériel OpenList pour la RAM, le CPU, plusieurs backends de stockage, le trafic proxy, les miniatures, aria2 et un déploiement pratique de ZimaOS.
OpenList hardware requirements at a glance
Size OpenList 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
- Persistent /opt/openlist/data plus optional thumbnail/temp/download data
- Docker
- Official image: openlistteam/openlist:latest
- Ports
- 5244 and 5245 exposed by the official image
- Best Zima starting point
- ZimaBoard 2 832
From official requirements to the right setup
Start with upstream facts for OpenList, then size the workload rather than copying generic container labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Number of storage mounts
- Proxy/direct mode
- Thumbnail generation
- aria2 use
- Local storage size
- Concurrent users
- Cache/temp paths
- Backup of app data
Official minimum requirements
OpenList documents Docker, ports, users, and optional images but no numerical whole-host CPU, RAM, or disk minimum.
Do not infer an official minimum from container metadata. OpenList itself is light; local file serving, FFmpeg thumbnails, aria2 downloads, and proxy throughput determine practical sizing.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Thumbnail and proxy workloads drive CPU. | |
| No numerical official minimum published | Depends on mounts and optional helpers. | |
| openlistteam/openlist:latest | Stable v4 image. | |
| UID/GID 1001 by default | Permissions must allow mapped-directory access. | |
| 5244 and 5245 | Check host conflicts. | |
| ffmpeg, aria2, aio | Enable only when needed. | |
| Not required | No GPU baseline. |
When to upgrade your hardware
Thumbnail workload
Proxy/download traffic
Local storage growth
Plan hardware growth with confidence
SSD app/cache
Keep OpenList data and thumbnail cache on SSD.
SSDMore RAM
Useful with many services or large shared-host workloads.
Higher-RAM hostLocal storage pool
Use ZimaCube when OpenList fronts a large local library.
Multi-bay storageCPU/network upgrade
Useful for many users, thumbnails, and proxy-heavy access.
Higher-throughput CPU/networkCan it run on ZimaOS?
Install OpenList from the ZimaOS App Store
A specific public OpenList App Store page is available.
Open OpenList in the ZimaOS App Store ↗Use the official OpenList image
Upstream documents openlistteam/openlist:latest and current permission rules.
Open OpenList Docker docs ↗Choose helper images deliberately
Use ffmpeg, aria2, or aio variants only when those workloads are required.
Review OpenList image variants ↗Zima hardware for OpenList
OpenList is usually a light control layer; file proxying, thumbnails, local storage, and offline downloads determine the hardware tier.
Choose by workload
ZimaBoard is sufficient.
Storage and CPU become more important.
Zima recommendations do not convert store metadata into upstream minima.
| 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 database, extraction, OCR, and multi-service workloads | Get Now |
| ZimaCube 2 Standard | Storage-heavy libraries, downloads, PDFs, podcasts, and retained uploads | Large persistent data sets where drive bays matter most |
|
8 GB RAM can be lower than ZimaBoard 2 1664 for memory-heavy services | Get Now |
| ZimaCube 2 Pro | CPU-heavier, database-heavier, and higher-concurrency workloads | Extraction, indexing, many users, or multiple demanding containers |
|
16 GB RAM can still constrain very large databases or local AI 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 OpenList need?
Upstream does not publish a numerical whole-host RAM minimum.
How many CPU cores does OpenList need?
No numerical official CPU minimum is published.
Which Docker image does OpenList use?
openlistteam/openlist:latest.
What ports does OpenList expose?
The current image exposes 5244 and 5245.
What changed with container permissions after v4.1?
The current container runs as the built-in openlist user with UID/GID 1001 unless you explicitly choose another user.
Can ZimaBoard 2 832 run OpenList?
Yes for common remote-storage and light local-storage use.
Does OpenList need a GPU?
No.
When should I choose ZimaCube 2?
For large local storage, thumbnail workloads, or high proxy/download throughput.
