OCI images and retained tags can grow much faster than the application metadata.
Teams hosting many images and releases.Wymagania sprzętowe Harbor: pamięć RAM, procesor i pamięć masowa
Zaplanuj sprzęt Harbor zgodnie z oficjalnymi wymaganiami ZimaOS: minimum 2 CPU, 4 GB RAM i 40 GB oraz zalecane 4 CPU, 8 GB RAM i 160 GB.
Harbor requirements at a glance
Harbor is a multi-container OCI registry and has one of the clearest upstream sizing tables in this batch.
- CPU minimum
- 2 CPU.
- RAM minimum
- 4 GB.
- Disk minimum
- 40 GB.
- Recommended
- 4 CPU, 8 GB RAM and 160 GB disk.
- Software
- Current edge docs require Docker Engine >20.10 and Docker Compose >2.3 for Compose deployment.
- Best Zima starting point
- ZimaBoard 2 832 matches or exceeds the official CPU/RAM minimum; ZimaCube 2 Standard/Pro is better when registry layers, replication and retention grow.
From official requirements to the right setup
Start with Harbor's official minimum/recommended table, then size actual registry storage separately.
-
Official requirements
Reserve at least 2 CPU, 4 GB RAM and 40 GB disk; the official recommended profile is 4 CPU, 8 GB RAM and 160 GB.
-
Confirm your needs
Estimate image layer growth, tags, retention, replication and vulnerability-scanning activity. Registry data can quickly exceed the baseline disk number.
-
Leave room to grow
Use reliable SSD-backed metadata/database storage and enough bulk capacity for OCI layers and backups.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with Harbor's official installer/Compose workflow, remap ports if 80/443 conflict, and persist the registry/database data.
Check every playback client
- Number of repositories
- Image/layer growth
- Retention policy
- Replication
- Vulnerability scanning
- HTTPS/domain
- Registry backup
- Other ZimaOS services
Official minimum requirements
Harbor's current installation prerequisites publish explicit minimum and recommended CPU, RAM and disk values.
The 2 CPU/4 GB/40 GB values are official minimums; 4 CPU/8 GB/160 GB is the recommended baseline. Registry content can still require much more storage.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU minimum | 2 CPU | Current official minimum. |
| RAM minimum | 4 GB | Current official minimum. |
| Disk minimum | 40 GB | Current official minimum. |
| CPU recommended | 4 CPU | Current official recommended value. |
| RAM recommended | 8 GB | Current official recommended value. |
| Disk recommended | 160 GB | Current official recommended value. |
| Compose runtime | Docker Engine >20.10 / Docker Compose >2.3 | Current edge documentation. |
When to upgrade your hardware
Harbor should scale when registry data, scanning or concurrent push/pull traffic outgrows the official baseline.
Registry layers approach storage limits
Scanning or replication increases CPU demand
Push/pull concurrency increases
Security scanning and replication add background compute and network activity.
CI/CD environments using Harbor as a central registry.More developers and runners can raise network, disk and service concurrency.
Busy build pipelines.Plan hardware growth with confidence
Scale Harbor by protecting registry storage and then adding CPU/RAM for background services and concurrency.
Move Harbor data to SSD-backed persistent storage
Database/metadata and active registry operations benefit from low-latency storage.
Use SATA/NVMe or ZimaCube SSD tiers.Use at least 8 GB for the recommended profile
Harbor's own recommended table uses 8 GB RAM.
ZimaBoard 2 832 already has 8 GB; 1664 gives more co-hosting headroom.Use multi-drive capacity for registry growth
OCI layers and backups can quickly exceed 160 GB.
ZimaCube 2 Standard.Use stronger CPU/network for busy registries
Scanning, replication and CI pull/push traffic benefit from stronger CPU and faster networking.
ZimaCube 2 Pro.Can it run on ZimaOS?
Harbor is not currently confirmed as a public official one-click ZimaOS App Store page in the sources checked for this guide. It can be deployed through Install Custom App using Harbor's official Docker Compose installer.
Custom install Harbor in ZimaOS
Use Install Custom App with Harbor's generated Docker Compose stack, persist registry/database data and resolve any 80/443 host-port conflicts before deployment.
Custom install Harbor in the ZimaOS app ↗Follow Harbor's official prerequisites
The current docs require at least 2 CPU, 4 GB RAM and 40 GB disk, with 4 CPU/8 GB/160 GB recommended.
Review Harbor prerequisites ↗Use Harbor's official installer workflow
Harbor supports deployment to a Docker host using Docker Compose or to Kubernetes using Helm.
Review Harbor installation ↗Choose Zima hardware for Harbor
Harbor has explicit upstream hardware numbers, making Zima comparisons more direct than for most apps.
Is this a small private registry or a larger CI/CD registry with scanning and retention?
Small private registry
ZimaBoard 2 meets the official CPU/RAM minimum; add at least 40 GB suitable persistent storage.
- Minimum-class fitZimaBoard 2 832
- More RAM headroomZimaBoard 2 1664
Larger registry or more CI traffic
Use multi-drive storage and stronger CPU/network as image retention and scanning grow.
- Storage-first platformZimaCube 2 Standard
- Higher-headroom platformZimaCube 2 Pro
Official minimum and recommended values do not guarantee registry capacity or CI throughput; image size, scanning and concurrency still matter.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small Harbor registries. | Harbor at or above the official CPU/RAM minimum with light CI traffic. |
|
Add at least 40 GB persistent storage; 32 GB eMMC alone is below the official disk minimum. | Get Now |
| ZimaBoard 2 1664 | Harbor with more services and memory headroom. | Registry, scanning and moderate CI plus other developer services. |
|
Still add sufficient external storage for registry data. | Get Now |
| ZimaCube 2 Standard | Storage-heavy Harbor registries. | Large OCI layer retention, backups and broader NAS duties. |
|
8 GB matches the recommended RAM value; storage topology is the main advantage. | Get Now |
| ZimaCube 2 Pro | Busier Harbor and CI environments. | Scanning, replication, concurrent push/pull and 10GbE-class networking. |
|
Actual CI throughput depends on image sizes, network and storage performance. | 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
These answers cover Harbor CPU, RAM, disk, Docker Compose, registry storage and ZimaOS deployment.
How much RAM does Harbor need?
Harbor's official minimum is 4 GB RAM and the recommended value is 8 GB.
How many CPUs does Harbor need?
The official minimum is 2 CPU and the recommended value is 4 CPU.
How much storage does Harbor need?
The official minimum is 40 GB and the recommended value is 160 GB, but registry layers can require much more.
Which Docker versions does Harbor require?
Current edge docs specify Docker Engine >20.10 and Docker Compose >2.3 for Compose deployment.
Does Harbor need an SSD?
SSD is not the published hard minimum, but fast persistent storage is strongly preferable for registry/database activity.
Does Harbor need a GPU?
No dedicated GPU is required.
Can ZimaBoard 2 run Harbor?
Yes. The 8 GB ZimaBoard 2 meets or exceeds the official CPU/RAM minimum, but external storage is needed because 32 GB eMMC is below the 40 GB disk minimum.
When should I choose ZimaCube 2?
When OCI layers, backups, scanning and CI traffic make larger storage and stronger CPU/networking valuable.
What sources informed this Harbor hardware guide?
Current Harbor installation prerequisites and deployment documentation plus current Zima product pages.
