How to add Portainer to Docker Desktop and connect it to a remote environment

Jack Wallen shows you how to extend the Docker Desktop feature set by adding Portainer into the mix.

EDITOR'S NOTE: This content was originally published June 2022 on TechRepublic. This information may be outdated depending on time of viewing.

Watch Tech Stories, a series of mini documentaries from TechRepublic:

[phenoumene]

nice thanks! could you please update the content?

[LostOnTheLine]

Is there any way to access the Docker Desktop Portainer Extension via a browser? I can only get to it on the machine it's on using "127.0.0.1:9000" or "localhost:9000" which is pointless if I'm already on that machine. Even from where I can there's no way in the extension to add a username & password.
Is the extension intended to be used solely for those who will not access it from another machine? That seems kinda needlessly limited

[LostOnTheLine]

Except... It doesn't work...
My other docker environment is on an older NAS so it unfortunately doesn't have the latest version, but you didn't give any "hows" or "whys". Like why port 2375? Another place I looked said to use port 2376. But neither said how to tell which port to use either.

It's very possible that my problem won't be solved even if you had the complete steps, but my biggest problem working with docker is that everyone seems to think there is only one way things work for everyone, & each of those people think that one way is different from every other person. But even running Docker desktop you could be running in WSL2 or not, I think you could even be running it in the old WSL1 if you wanted to for some reason. As for managing remote instances they could be running on other windows machines, on a Linux machine, on a Mac, on a Linux-based NAS, on a Synology NAS, on an Asustor NAS, on a Huckleberry Pie, & I've even heard of people running docker on a USB drive attacked to their Router, though that sounds really stupid, I guess it's possible. But those might not have the same ports used, maybe the system uses those ports for other things & Docker had to use a different one, maybe the version of Docker is older & uses a different one, maybe the user changed the port because they needed it for something else.

Since the port used is obviously not consistent how about telling us how to find the port to use on the system we want to connect & say "I'm running on a Huckleberry Pie & mine uses this port" or "I've tried this on several windows machines & a few Mac machines & they all use this port but if yours doesn't work do this to find out which port to use"

[RealEstateD]

That's low effort! ... in addition the interface changed and this video is outdated.