If you are reading this post, i will assume by now that you have heard/read the news of Docker EE’s acquisition by Mirantis, and their eventual sun-setting of Swarm within the next 2 years.
It’s important to me to explain to our user community that this does not materially impact Portainer or our vision.
Before a release is initiated, the entire Portainer team dedicate time to complete comprehensive testing of the portainerci/portainer:develop & portainerci/agent:develop images.
By popular demand, i will quickly show you the process to get Portainer and the Portainer Agent running in a Docker Swarm environment atop Windows Server 2019.
Note that due to a bug in Docker (https://github.com/moby/moby/issues/39577) we are unable to deploy the Portainer instance as a service at this time.
Now that the edge agent has been released, let me give a brief overview of how it works. Note that deep technical documentation will be made available in the agent repo on github in due course.
In standard deployments, the central Portainer instance and any endpoints it manages are assumed to be on the same network, that is, Portainer and the agents are able to seamlessly communicate to one another.
With the adoption of containers continuing to accelerate, we are seeing deployments of the Docker engine extending beyond the server. Containers are making an appearance in everything from storage devices and Ethernet switches, though to IOT monitoring/control equipment.
We have been asked for over a year now what our "Kubernetes Strategy" is, and our answer has always been the same:
"Portainer's sole reason for being is to simplify container platform operations; when Kubernetes gets simplified, we will integrate it into Portainer".
Well, we have come to a point where we now believe that its impossible to simplify Kubernetes to a level where we can verbosely pass through and visualize its plethora of functions 1:1, akin to what Kubernetes' native dashboard does.
Hi Portainer community..
It is with pleasure that I am able to announce the release of Portainer 1.21.0. This release enables two pretty big new features, which i wanted to explain more about below..
_________________________________________________________________________
First off, we are happy to add support for Role Based Access Control (RBAC), available as a paid extension which you buy "in-app" via the extensions page.
So I had the great pleasure to attend DockerCon in San Fran this year, and what a DockerCon it was. It seems every year the number of "its my first ever DockerCon" attendees keeps increasing, which is a great sign for the technology's adoption.
This year i decided to host a number of hallway tracks, and also ran a beer and pizza meetup on the monday night prior to DockerCon.
As the open source core, Portainer CE remains very much a live project within the open source community. Since June 2018, the Portainer.io team has released versions 1.18.0 through 1.20.2 with a range of new features and capability. If you haven’t tried Portainer recently, here’s what you will find:
Agent Support – If you are using a distributed Docker environment, you can now deploy an agent to your remote Docker Hosts (Windows or Linux, Swarm or Standalone), negating the (arguably risky) need to expose your Docker daemon externally.
This week we received an interesting support request, and i thought i might be useful to share..
The user was stating that on their docker deployment, Portainer was unable to connect to /var/run/docker.sock regardless of correctly configuring the CLI command.