Requirements and prerequisites
Requirements specific to your environment will be covered in the installation process.
Valid configurations
Every Portainer release goes through functional, release and post-release testing to ensure it works as expected. Because we cannot test against every configuration variant out there, we test against a subset.
The following tables list all of the configurations that we have tested, validated and consider to be functional. If a variant is not listed, it doesn't mean it won't work, it just means it hasn't been tested.
A note on Podman support
At present, Portainer does not fully support running on Podman environments. While some aspects of Portainer do function with Podman, it isn't a platform that we test on or build for, and there are known issues. We currently do not have an ETA on when full Podman support will be implemented in Portainer.
Portainer Business Edition (BE)
Portainer Community Edition (CE)
If you find an issue with an unlisted configuration, before reporting a bug, update your environment to a valid configuration and try to replicate the issue.
Persistent storage
The Portainer Server requires persistent storage in order to maintain the database and configuration information it needs to function. The installation process provides a basic storage configuration for your platform. By default, both Docker and Kubernetes provide local (to the node) storage only, and if cluster-wide persistent storage is desired we recommend implementing it at the infrastructure level (for example, via NFS).
Additionally, you will want to ensure that your persistent storage for Portainer's data volume is right-sized for your needs. If you intend to use Portainer's Git deployment functionality for example, you will need to be aware that as part of the deployment from Git, Portainer will clone the remote repository locally to the Portainer data volume, which in the case of larger or multiple Git repos may consume significant amounts of disk space.
Ports
In order to access the UI and API, and for the Portainer Server instance and the Portainer Agents to communicate, certain ports need to be accessible.
On the Portainer Server the following ports must be open:
TCP port
9443(or30779for Kubernetes with NodePort) for the UI and APITCP port
8000(or30776for Kubernetes with NodePort) for the TCP tunnel server for Edge Agents. This port is optional and only required if using Edge Compute features with Edge Agents.
For the Portainer Agent:
TCP port
9001(or30778for Kubernetes with NodePort) must be accessible on the Agent from the Portainer Server instance.
The Portainer Edge Agent does not require any open ports.
All ports can be changed during installation.
Last updated