Portainer Update, March 2020..

Hi Portainer fans... time for a little update..

Sorry for the long delay between blog posts, but our little team has been kept quite busy building support for Kubernetes into Portainer, working on our next release, and extending our Edge Compute functionality.. all good things, but no excuse for our silence 🙂

Anyway, here is what we have going on.. prepare to get excited..

First off, we were delighted to have welcomed two new developers into the Portainer family, Chaim, and Maxime. These devs are highly competent in Portainer's development languages, and will complement our existing developers nicely. We are really looking forward to their help ensuring we keep to committed development timelines.

In the next few days you will see us release Portainer 1.23.2, which is a minor release, but one that includes fixes for three gnarly bugs; support for Named Pipes on Windows 10, fix a long standing issue with RBAC and LDAP, and a fix for the broken container health status filter. These three bugs have caused our users pretty significant inconvenience, and so its good we finally have a resolution for them.

Note that through the testing of 1.23.2, we found four new bugs in relation to Docker on Windows platforms. We spent many hours trying to find workarounds and/or fixes, but in the end, elected to wait for Docker (Moby and/or Docker Desktop) to resolve the underlying issues. You can read more about this here. These impact the usability of Portainer on Windows platforms, so you should double check your use case against that article.

Portainer 1.23.2 is targeted to be our last release in the 1.XX chain, as we focus on moving to a Portainer 2.0 release in Q2. This 2.0 release will, among other things, add support for Kubernetes endpoints (whilst retaining full support for Swarm and Standalone). If between the 1.23.2 release and the release of Portainer 2.0, we find an urgent need to release another version, then we will do so, but our primary focus is now on the 2.0 release.

Speaking of Kubernetes support, we will be releasing our Beta of Kubernetes on the 31st March. Watch out for a specific announcement on this, but it goes without saying ,we are extremely excited by what we have created. We believe the simplicity we have bought to Kubernetes is a game changer. I myself have never once deployed ANYTHING from the Kubernetes CLI (wouldnt know how), yet I am able to deploy even relatively complex application setups using Portainer Beta for Kubernetes. This bodes well for mainstream uptake of this technology. We plan to keep the Beta in the market for 1 month, gathering feedback, and then incorporating that feedback into the final version, which will then be merged into Portainer 2.0. Note for clarity, we will have ONE version of Portainer that includes support for Docker Standalone Hosts, Docker Swarm Clusters, AND Kubernetes Clusters.

Finally, we are launching Portainer Support Subscriptions this week, so if you use Portainer, and you could benefit from formal support, then these are for you... simply click the "Portainer Support" icon in the top right of your Portainer instance for more info, or visit our website to read more.

That's all for now, keep an eye out for our 1.23.2 release and the BETA of Portainer for Kubernetes...

Neil Cresswell

Co-Founder, and CEO



          • instructions how to update via docker please


          • Neil Cresswell

            depends how you deployed Portainer…
            If you deployed Portainer as a stack, then you simply go into “services” click on the portainer_portainer service, click “update the service” and then select “pull latest image”. then wait 30 seconds… after that you can ctrl shift R to refresh the page and relogin to the new version.

            If you deployed as a container, then you must go back to the CLI.. docker stop portainer, docker rm portainer, then redeploy portainer using the command from our website. Just reuse the existing persistent volume.


          • Neil Cresswell

            I have now posted a youtube on how to do this: https://youtu.be/arATxHUyTlY


      • Can’t wait till the beta comes out! I’ve spun up two of my own k3s clusters yesterday, not a big fan of the Kubernetes Dashboard, seems like a bunch of hoops to jump through to safely expose it outside of the cluster.

        I’m assuming that your still on track to deliver this beta tomorrow regardless of the lock-down (assuming the core team is in Auckland)? What time should we expect this if so?



      • Neil Cresswell

        We are releasing as planned tomorrow, and likely to be the evening. Make sure to join our free membership program, and then register for the founders webinar for a walkthrough of this K8s version. (webinar is 7am NZDT Wed Morning).


    • I dont use Kubernetes, and im just a home user, however i see they have an app, I have some containers inside of docker i need to keep an eye on from time to time, a great way to do this is portainer, but what if im not at a computer, and i just have a mobile phone, you can see where im going with this, it would be nice to see a portainer/docker app for ios and android, i would pay for this! a one off fee…


    • Neil Cresswell

      Pretty hard for us to create a mobile app as there is a lot of logic in the front end.. would need to be a mobile app that talks to the front end, which is kinda ugly.


Leave a comment!

All fields marked with an asterisk* are required.