Issue: Portainer HTTPS Port Change - 9442

[salieri]

@MichaIng

Ah so, when adding a BE license key, Portainer upgrades itself?

Yeah, that’s what I painfully learned by going through this entire forum post exercise unfortunately…

@MichaIng

Hmm, then looks like, to be failsafe we would really need to detect BE vs CE and and install the variant previously used

I would agree if that works for you guys.

The BE is still free - Link: Take 3 - Get your first 3 nodes free

@MichaIng

if there is no other reason to switch to CE, you can update the BE version with HTTPS port exposed like this:

There isn’t a reason to downgrade. It’s free and has more features. Why not I guess. Thanks for the guidance you posted below.

[MichaIng]

I also just found the old image: https://hub.docker.com/r/portainer/portainer
Changed 3 years ago, hmm, well does not hurt to detect and in case remove that one as well.

This should do:

dietpi-software: Portainer: handle BE correctly

[Joulinar]

@MichaIng

@Joulinar do you remember why we check for /portainer/portainer as well as /portainer/portainer-ce?

/portainer/portainer was the name of the image in the past. But changed to CE and EE some years back

[MichaIng]

Right, found the image above, split soon 4 years ago. Not relevant anymore, but still detecting and upgrading it correctly did not add much code when we need to differentiate between CE and BE anyway.