Welcome to the official Portainer Documentation. This is an open source documentation project and all community contributions are welcome and encouraged. For information about contributing to the Portainer documentation, see Contribution guidelines.
Portainer Community Edition 2.0 is the foundation of the Portainer world. With over half a million regular users, it’s a powerful, open source toolset that allows you to easily build and manage containers in Docker, Docker Swarm, Kubernetes and Azure ACI.
Portainer hides the complexity of managing containers behind an easy to use GUI. By removing the need to use the CLI, write YAML or understand manifests, Portainer makes deploying apps and troubleshooting problems so simple that anyone can do it.
The Portainer development team is here to assist you on your container journey. You can engage with them any time through our community-based support channels.
Knowledge Base and FAQs
As the Portainer community continues to grow, we continue to support the community to the best of our ability.
To streamline our operations and allow us to focus on delivering the right support and features in the right areas at the right time we encourage you to refer to our comprehensive Knowledge Base for any queries you may have.
If you can't find what you're looking for in our Knowledge Base then please refer to one of the support channels listed below.
As a free and open source product, we have been heavily reliant on our community to provide "how to" support to our community, recently, we have invested significant time in improving and updating our documentation found on this site and our YouTube channel. While we endeavour to cover as many scenarios as possible, there may be some that our documentation doesn’t cover.
QUESTIONS should be posted to either Github Issues or to the community Slack channel. While we offer other platforms for questions (Reddit, Discord, Stack Overflow) the Portainer team will be less active in these.
Suspected BUGS should be posted to Github. There they will be appropriately managed by our support and development teams.
VULNERABILITIES should be emailed to email@example.com and will be dealt with immediately.
ISSUES IN OUR DOCUMENTATION can be raised through our Github Documentation Channel, or you can follow the user-contribution guidelines.
We will not provide support over email.