premiumizer VS Portainer

I'm using Premiumizer, in my case in Docker.

if you need a visual way to understand this, try portainer (https://www.portainer.io/). the community edition is free

FWIW, upgrading my Synology installation manually "worked," but then I ran into known issue #8461 and had to roll back to CE. Unfortunately, when attempting to roll back the database as described here, it resulted in "failed rolling back to CE | error='object not found inside the database'". Replaced the DB with a backup, fired up the CE container, and all is well, albeit with a fair amount of time lost in troubleshooting and rolling back. Hope this gets sorted out soon.

We're aware of some issues with the in-app upgrade on Synology platforms at the moment and have an internal issue open around this. We're tracking this in our Github issues and in the meantime you can do a manual upgrade - have a look at our documentation for info on this.

If an app can be installed through the Store, I'll do it in the Store. Only if it's unvailable that way, will I use the terminal. An example I'd use the terminal with, would be OpenSnitch. I also use the GUI for docker, with Portainer as a frontend.

There's an option to make this more subtle in 2.17.1. https://github.com/portainer/portainer/issues/8517

Without being too cheeky, it certainly isn't the new ads that are implemented for BE upselling: https://github.com/portainer/portainer/issues/8452

Docker is certainly not marketed that way & even the majority of tutorials / if not all on Digital ocean or similar sites don't misguide you into doing this. It is clearly not marketed as "usable without reading docs" and even though people using it as a tool to deploy prebuilt software without learning its configuration, this doesn't apply to the docker commands itself.

If https://www.portainer.io/ would do this __implicitly__, your argument would be more valid. But for the docker command-line it's a bit too far-fetched.

Portainer

Are you able to open a bug report in our GitHub repository if you haven't already? This way we can gather feedback from other users that might be hitting this too, as well as flag it with the development team to dig into further.