“Socket”ing it to you: switch from Docker socket to Portainer Agent

Hi Portainer fans... hope everyone is well in this rather challenging time..

For the vast majority of users, they initially deploy Portainer using our exceptionally simple "single command quick-start (docker run)", which is great when you are just starting out with Portainer, on a single Docker Host, and when you are not using Swarm. But what happens when your needs change, and you would like to start using Swarm and some of the more advanced Portainer features? How can you switch your Portainer deployment from being the simple one-liner deployment to the version that leverages the exclusive Portainer Agent?

This is one of the most asked about topics on our support channel – and one of the easiest to resolve as making the switch from Docker socket to the Portainer agent has been kept as simple as it can be.

So simple in fact, we’ve been able to cover all the steps to upgrading in a short (8 minutes 22 seconds) “how to video” that covers:

  1. How to upgrade your Portainer instance when you have it deployed to a local standalone Docker host.
  2. How you upgrade that host to Docker Swarm and then,
  3. How you transition to the Portainer agent.

The ‘how to’ should be of real interest to anyone wanting to get compose v3 support, use the volume browser feature as well as learning the swarm/orchestration concepts. All of which are really valuable capabilities to have in managing Docker.

Even if you have been using Portainer for a while it could be a useful 8 minutes to check you’ve got everything you could deployed and working as it should.

If you’re a Docker user looking for more information on switching to Portainer we’ve got a number of how-to documents, which are available exclusively (free) to Portainer members, and there is of course always our searchable Portainer Documentation section under Support on the website.

If you’ve got any questions on this, even after you’ve watched the video – please don’t hesitate to get in touch.



Leave a comment!

All fields marked with an asterisk* are required.