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.

Portainer Business Edition (BE)

Portainer Version

Release Date

Docker Version

Kubernetes Version

Architectures

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).

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. The Portainer Server listens on port 9443 for the UI and API (or on 30779 for Kubernetes with NodePort) and exposes a TCP tunnel server on port 8000 (or on 30776 for Kubernetes with NodePort). This second port is optional and only required if using Edge Compute features with Edge Agents. The Portainer Agents listen on port 9001 (or 30778 for Kubernetes with NodePort).

All ports can be changed during installation.

PreviousPortainer architecture NextInstall Portainer

Last updated 2 years ago