Portainer version - how do I update to version 2.1.1?

Configuration
1

This morning, when opening the Portainer supervisor addon, I had a message:

Portainer CE 2.1.1 is here. Now with support for Compose >3 in standalone hosts, and Compose 3.8 for Swarm. Upgrade today! https://bit.ly/3p4IDO5

I would like to run the latest version, but no update/upgrade path is offered under home assistant from version is 1.24.0 installed by the addon.

Can I update portainer and keep running it under the home assistant console or do I have to uninstall the portainer addon, install portainer as a new container under the new docker and run it from Debian rather than home assistant?

2

Well I rarely use supervised docker unless I have too… so I believe you should run portainer from debian instead.

3

I believe Frenck maintains that add-on (could be wrong), and it will only get updated when/if he has the time to do it.

Unless there is some new feature that you can not live without in the latest Portainter, which is highly unlikely, just wait for it to be updated in due course.

No.

4

Neither statement is that black & white.

there are valid uses for both.

But I vote for the first. :laughing:

5

Agree 100%

My Portainer loads from a docker-compose file and I use it in an iFrame in HA. If I get a docker update for instance, Portainer will restart immediately and I can at least see the status of all other containers inc Home Assistant ones. If you use the addon you can’t do that.

As well as running the latest Portainer on my Supervised install, I see no downsides in doing this and lots of reasons to not use the official addon in this instance.

2 Likes
6

yup… I even add my 2nd docker machine to the list. So I can monitored both.

7

I have pihole set up as a container and can see it in the addon portainer. I tried panel iframe:

panel_iframe:
  pihole:
    title: "PiHole"
    url: "http://192.168.254.200/admin/"

When I click on PiHole, I get “refused to connect”

I’ve posted another thread on this…but how did you do it? I"m thinking that maybe the /admin part is not valid…but that’s not documented.

8

My iFrame loads Portainer as https not http… if your HA is https then iFrames must also be https. (I have a sub domain for Portainer)

9

I am not (yet) using https…strictly http. I’m new to docker…I followed the “manual” to get pihole installed…so it has the same ip as HA with /admin. Likely there is a (hopefully easy) way for the pihole container to have it’s own IP…but not sure where to look.

10

Portainer should show you the ipad dress of the container. I assume you realise pinhole is deprecated now? Have you considered using adguard?

11

I know pihole is depreciated which is why I installed it in it’s own container. I don’t see any network for that container in portainer…I just see open ports. The networking tab doesn’t have any entry for pihole in the list of networks.

Q: can i just remove portainer addon in HA and install it in it’s own container without having to reinstall HA? That’s my goal…I’m just using pihole to see if iframe works…and it doesn’t

12

I created a 2.1 version of the add-on if you want to continue to use the add-on within HA rather than as a separate standalone container.

13

I have like a lot of you I suppose, multiple RPIs/devices in the house on which I’ve installed a Docker/Docker Compose/Portainer. I’m planning to move all of them to the IOTstack. But in any case, I’m looking for a way to control them centrally in Home Assistant. Any ideas ?