Databases, media servers, automation, observability and other Docker workloads can dominate system resources while Portainer remains relatively light.
Users whose Docker host is swapping, CPU-saturated or repeatedly constrained under application load.Configuration matérielle requise pour Portainer : processeur, RAM, stockage et hôtes Docker
Découvrez la configuration matérielle requise par Portainer pour le processeur, la RAM, le stockage, Docker, les agents, les données persistantes et les hôtes de conteneurs ZimaOS.
Portainer hardware requirements at a glance
Portainer is a container-management control plane, not the workload it manages. Current Portainer documentation does not publish one universal CPU or RAM minimum for a Portainer Server; size the host separately for Portainer itself and for the containers, databases, media servers or other services that Portainer manages.
- CPU
- Current Portainer documentation does not publish one universal CPU model or core-count minimum for the Portainer Server. Portainer itself is lightweight relative to most application workloads; CPU demand grows mainly with environment count, API/UI activity and the workloads sharing the same Docker host.
- RAM
- There is no current official universal RAM minimum for Portainer Server. Do not convert Raspberry Pi examples or Portainer Run application limits into a Portainer Server memory requirement.
- Storage
- Portainer Server requires persistent storage for its database and configuration. The data volume can also grow when Portainer clones Git repositories for stack deployments, so persistent storage should be sized beyond the base application footprint.
- Runtime and architecture
- Current Portainer requirements list ARM64 and x86_64 as supported architectures. The Docker-on-Linux CE installation path requires a working current Docker installation and creates a persistent portainer_data volume.
- Network
- Portainer Server uses TCP 9443 for the UI/API. TCP 8000 is optional for Edge Agent tunnel features, while Portainer Server must be able to reach a standard Agent on TCP 9001 when that connection method is used.
- Best Zima starting point
- ZimaBoard 2 832 is already more than enough for Portainer itself and a light home Docker host. Move to 1664 or ZimaCube 2 when the containers, databases, storage, virtual machines or environment count—not the Portainer UI alone—need more resources.
From official requirements to the right setup
Portainer sizing starts by separating the management plane from the workloads it controls, then checks runtime compatibility, persistent data, environment count, network paths and the other services sharing the ZimaOS host.
-
Official requirements
Identify what Portainer is managing. A Portainer Server that only manages a few Docker containers has very different host requirements from a system that also runs databases, media servers, AI models or many remote environments.
-
Confirm your needs
Match the deployment method to current Portainer requirements. For the Docker-on-Linux CE path, keep Docker current and working, use a supported architecture, and retain the persistent Portainer data volume.
-
Leave room to grow
Plan Portainer's own persistent storage separately from application data. Portainer stores its database and configuration and may also clone Git repositories locally for stack deployments, while container volumes belong to the managed workloads.
-
Run it on ZimaOS
Install the ZimaOS Portainer app, verify UI access and managed-environment connectivity, then observe CPU, memory, disk latency and Docker-host pressure during the workloads you actually run before upgrading hardware.
Check every playback client
- Deployment type: local Docker, Swarm, Kubernetes, Podman, Agent or Edge Agent
- Portainer edition and current release compatibility
- Host architecture: x86_64 or ARM64
- Docker or orchestration version compatibility
- Persistent Portainer data volume and backup plan
- Git-based stack deployment storage growth
- Ports and reachability for 9443, optional 8000 and Agent 9001
- CPU, RAM, storage and GPU needs of the containers Portainer will manage
Official minimum requirements
Portainer's current official documentation defines supported configurations, persistent storage, ports and installation prerequisites, but it does not publish one universal Portainer Server CPU/RAM minimum.
Treat Portainer as a lightweight management layer and size the physical host primarily from the Docker or cluster workloads it will run. Do not promote third-party Raspberry Pi recommendations or Portainer Run application limits into official Portainer Server minimums.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU minimum | No universal official minimum published | Current Portainer Server requirements do not define one processor model or core-count floor. |
| RAM minimum | No universal official minimum published | Current Portainer Server requirements do not define one fixed system-memory floor. |
| Architectures | ARM64 and x86_64 | Current supported-configuration tables list both architectures for Portainer. |
| Docker-on-Linux prerequisite | Working current Docker installation | The current CE Docker-on-Linux installation guide starts from a working current Docker setup rather than a Portainer-specific CPU/RAM specification. |
| Persistent data | Required | Portainer Server needs persistent storage for its database and configuration; Git-based deployments can add repository clones to the Portainer data volume. |
| Server connectivity | 9443 required for UI/API; 8000 optional for Edge Agent tunnel | A standard Portainer Agent must be reachable on TCP 9001 from the Portainer Server when that connection method is used. |
When to upgrade your hardware
Upgrade the host when the complete container platform shows a real resource bottleneck, not because Portainer itself is present.
The managed containers need more memory or CPU
Portainer data and stack workflows outgrow basic storage
You are consolidating a larger homelab onto one machine
More environments, backups, configuration history and Git-based stack deployments increase the value of responsive persistent SSD storage and a larger application-data pool.
Users managing many stacks, repositories or a broader long-running container platform.Portainer can manage a small host easily, but the physical server may need more RAM, CPU, network and storage once it also carries many services, VMs or high-I/O containers.
Users moving from a simple Docker appliance to an all-in-one home server or NAS.Plan hardware growth with confidence
Portainer scales best when management needs and workload needs remain separate in the hardware plan.
Keep Portainer on a compact always-on Docker host
For a small household stack, Portainer can stay on the same low-power x86 server as the applications it manages.
ZimaBoard 2 832Add RAM for a denser container stack
Choose more memory when databases, monitoring, automation and multiple applications share the same host. The extra RAM benefits those services rather than making Portainer itself intrinsically faster.
ZimaBoard 2 1664Move container data to a multi-drive platform
A larger NAS-class system becomes useful when persistent application data, backups and Docker volumes—not the Portainer database alone—need more storage capacity and redundancy.
ZimaCube 2 Standard or ProAdd GPU only for GPU-dependent containers
Portainer has no dedicated GPU requirement. A GPU is justified only when a managed workload such as local AI, video processing or another accelerator-aware container independently requires it.
ZimaCube 2 Creator Pack only for separate GPU workloadsCan it run on ZimaOS?
Portainer Community Edition is available in the current ZimaOS App Store. Verify the Portainer management plane and the Docker workloads separately after installation.
Install the current ZimaOS Portainer app
ZimaOS currently lists Portainer Community Edition as a container-management application, so a normal ZimaOS deployment does not require you to build Portainer manually from source.
Open Portainer in the ZimaOS App StorePreserve Portainer's persistent data
Portainer Server needs persistent storage for its database and configuration. Back up the Portainer data volume together with the Docker stack definitions and application data you need to recover.
Review Portainer requirementsValidate Docker and network reachability
For Docker deployments, keep the runtime on a Portainer-supported version and verify 9443 for UI/API plus Agent or Edge-Agent connectivity only when those features are used.
Review the Docker-on-Linux install pathWhich Zima hardware fits Portainer?
Portainer itself is not a reason to buy a large server. Choose hardware from the number and type of containers, persistent-data volume, database activity, storage layout and network traffic that Portainer will manage.
Is Portainer managing a light household Docker stack, or is the same machine becoming a larger multi-service homelab/NAS?
Light-to-moderate local Docker host
Start with ZimaBoard 2 832. Its Intel N150 and 8 GB RAM are already far beyond what a Portainer-only control plane needs. Choose 1664 when the surrounding container stack independently needs more memory.
- Portainer plus several lightweight containersZimaBoard 2 832
- Denser container stack with databases or more servicesZimaBoard 2 1664
Storage-heavy or larger all-in-one homelab
Choose ZimaCube 2 when the system also needs multi-drive storage, more compute, heavier I/O or broader self-hosting. Creator Pack is justified only when a managed workload has a real GPU requirement.
- Storage-first Docker/NAS hostZimaCube 2 Standard
- Heavier multi-service and higher-I/O hostZimaCube 2 Pro
- Only when managed AI/creator workloads need a dedicated GPUZimaCube 2 Creator Pack
These recommendations size the whole ZimaOS/Docker host, not a fixed Portainer Server minimum. Portainer publishes no universal CPU/RAM floor, and a GPU provides no Portainer-specific benefit.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | The best-value current Zima option for Portainer plus a small-to-medium household Docker stack. | Portainer, dashboards, network utilities, lightweight automation and several ordinary self-hosted containers. |
|
The 32 GB eMMC is the practical constraint before Portainer CPU becomes an issue. Use SSD/SATA storage for a persistent container host with growing images and volumes. | Get Now |
| ZimaBoard 2 1664 | A compact Portainer host with more RAM for databases, monitoring and a denser Docker stack. | More containers, PostgreSQL/Redis-class services, observability, automation and other memory-consuming applications. |
|
Do not claim Portainer needs 16 GB. Choose 1664 only when the managed workloads or additional services need the extra memory. | Get Now |
| ZimaCube 2 Standard | A storage-first Docker/NAS host managed through Portainer. | Persistent application volumes, backups, media/data services and a moderate multi-container ZimaOS environment. |
|
Standard still has 8 GB RAM. If memory pressure is the main issue and multi-drive storage is not required, ZimaBoard 2 1664 may provide more RAM headroom at smaller scale. | Get Now |
| ZimaCube 2 Pro | A larger all-in-one homelab where Portainer manages many services and substantial persistent data. | Heavier multi-container stacks, databases, backups, storage services, VMs and higher-I/O self-hosting. |
|
Do not recommend Pro merely for more Portainer environments if the managed workloads are light. Upgrade when compute, RAM, storage or network demand is proven. | Get Now |
| ZimaCube 2 Creator Pack | A Portainer-managed server that also runs separate GPU-dependent AI or creator containers. | Local AI, GPU-accelerated media or creator workloads alongside normal Docker services and storage. |
|
Extreme overkill for Portainer alone. Never use Portainer's presence to justify a GPU purchase. | 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
Common Portainer sizing questions become easier once the management plane is separated from the containers and infrastructure it controls.
How much RAM does Portainer need?
Current Portainer Server documentation does not publish one universal RAM minimum. Size the host from the managed containers, environment count, databases and other services, then leave headroom for Portainer and Docker themselves.
How many CPU cores does Portainer require?
There is no current universal official core-count minimum for Portainer Server. A modern low-power CPU is sufficient for ordinary home use; CPU upgrades are usually driven by the applications running on the Docker host.
Does Portainer need an SSD?
Portainer requires persistent storage, and current official guidance favors low-latency, high-throughput storage for larger or performance-critical deployments. For a home server, SSD storage is a sensible place for Portainer data, Docker metadata, databases and active application data.
Does Portainer need a GPU?
No. Portainer's management UI and API do not require a dedicated GPU. A GPU matters only when one of the containers Portainer manages needs GPU acceleration.
Can Portainer run on a Raspberry Pi?
Yes on supported ARM64 configurations. The supplied SunFounder guide recommends a Raspberry Pi 4 with 4 GB or more RAM or a Pi 5 for its tutorial, but that is third-party platform guidance rather than an official Portainer Server minimum.
Is 4 GB RAM an official Portainer minimum?
No. The 4 GB figure in the supplied Raspberry Pi guide is that author's recommended Pi setup, not a current Portainer Server minimum. The supplied 2021 GitHub issue also contains a request for minimum hardware figures but does not establish one.
Do the CPU and memory numbers on docs.portainer.ai define Portainer Server requirements?
No. That page is Portainer Run documentation and describes default resource requests and limits for applications deployed through Portainer Run. Those values must not be republished as Portainer CE/BE Server hardware minimums.
What should I upgrade first for a larger Portainer home server?
Upgrade the resource that the managed workloads actually exhaust: RAM for a denser container stack, SSD capacity/IOPS for databases and volumes, more CPU for compute-heavy services, or more network/storage capacity for NAS and multi-service use.
What sources and further reading informed this Portainer hardware guide?
The current Portainer requirements and Docker-on-Linux installation pages are the primary sources: they define supported configurations, persistence, ports and Docker prerequisites but do not provide one universal CPU/RAM minimum. GitHub issue #5406 is a 2021 user request for missing minimum hardware figures and contains no authoritative minimum. The SunFounder page is a 2025 Raspberry Pi deployment guide recommending Pi 4 with 4 GB+ RAM or Pi 5 and SSD/NVMe for its use case; it is third-party deployment guidance, not an upstream minimum. The supplied docs.portainer.ai page belongs to Portainer Run and its application resource requests/limits do not describe the Portainer Server itself.
