this is what it shows me when I login (so I guess the EE version is what is used for managing?).
I guess there is still a misunderstanding an what Portainer is and what it does. It doesn’t manage actively any images. It is just a frontend for the Docker command line. It has no direct relation to other images. You could start/stop/create container. But same you could do on CLI. Removing Portainer will have no impact to any other container. According to your screenshot, Portainer EE is running on port 9002 (same as our installer would use) It seems up and running. Therefore, you should be able to connect. Usually, Portainer EE require a business license.
Our DietPi script will not update or touch the EE version. We explicitly install/manage CE
I just updated from CE to Business because the license was free (today). I guess I could just remove the unused image here?
it is not about images, above you tried to bring up a CE container with same name as already running EE container. Therefore you failed. You need to make yourself clear an what you like. To continue using EE version or the regualr CE. In case of EE, you need to mange updates yourself or you go back to CE and could use our scripts.
oh, I did not realise the versions were that different. I just want an uptodate portainer and the BE seemed “better” than the CE version (which never update automatically by the way). so I thought BE would do the trick and inserted the license.
that’s why we offer the reinstall option on dietpi-software. BTW: nearly all Docker containers don’t update automatically. For such functionality, some people developed Watchtower
1 Like
ok, how to roll back and not screw it up completely?
are you able to connect via SSH and share following
docker container ls --all
It’s hard to copy conatiner ID’s from your screen shot.
sure:
posted via text.
pls don’t do screenshots. Connect via SSH and copy content directly.
docker container ls --all
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b52877869b89 portainer/portainer-ee:2.17.0 "/portainer" 8 hours ago Up 7 hours 8000/tcp, 9443/tcp, 0.0.0.0:9002->9000/tcp, :::9002->9000/tcp portainer
1d0f463d370a portainer/portainer-updater:latest "/portainer-updater …" 8 hours ago Exited (0) 8 hours ago portainer-upgrade-1679585048-2-17-0-updater-1
4183b87ff3c1 rustdesk/rustdesk-server:latest "hbbs -r …" 3 months ago Up 7 hours 0.0.0.0:21115-21116->21115-21116/tcp, :::21115-21116->21115-21116/tcp, 0.0.0.0:21118->21118/tcp, :::21118->21118/tcp, 0.0.0.0:21116->21116/udp, :::21116->21116/udp hbbs
07b743bc23f4 rustdesk/rustdesk-server:latest "hbbr" 3 months ago Up 7 hours 0.0.0.0:21117->21117/tcp, :::21117->21117/tcp, 0.0.0.0:21119->21119/tcp, :::21119->21119/tcp hbbr
c244da73ea8d jc21/nginx-proxy-manager "/init" 4 months ago Up 7 hours 0.0.0.0:80-81->80-81/tcp, :::80-81->80-81/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp npm
root@DietPi:~#
do a dietpi-backup first. Once complete, remove Portainer EE and Update container
docker container rm -f b52877869b89
docker container rm -f 1d0f463d370a
dietpi-software reinstall 185
looks fine now, but I cannot access portainer anymore with “localIP”:9002
this is what it shows me now:
docker container ls --all
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8595f7799a27 portainer/portainer-ce "/portainer" 3 minutes ago Restarting (1) 45 seconds ago portainer
4183b87ff3c1 rustdesk/rustdesk-server:latest "hbbs -r …" 3 months ago Up 3 minutes 0.0.0.0:21115-21116->21115-21116/tcp, :::21115-21116->21115-21116/tcp, 0.0.0.0:21118->21118/tcp, :::21118->21118/tcp, 0.0.0.0:21116->21116/udp, :::21116->21116/udp hbbs
07b743bc23f4 rustdesk/rustdesk-server:latest "hbbr" 3 months ago Up 3 minutes 0.0.0.0:21117->21117/tcp, :::21117->21117/tcp, 0.0.0.0:21119->21119/tcp, :::21119->21119/tcp hbbr
c244da73ea8d jc21/nginx-proxy-manager "/init" 4 months ago Up 3 minutes 0.0.0.0:80-81->80-81/tcp, :::80-81->80-81/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp npm
root@DietPi:~#
the container is not coming up correctly. Can you check following
journalctl -u docker.service
there on the last line, you see the link you need to check to downgrade from EE to CE
already on it. will post news.
on step 2 the command includes “ubuntu”. is that still compatible with dietpi commands?
you should be able to skip step 2. I already created the backup I guess using dietpi-backup
update: dietpi pulled the necessary files for ubuntu itself. rollback went fine. I can verify this by looking at the yellow “UPGRADE to BE” nag 
so now watchtower is the way to keep everything (even portainer?) up to date?