how did you install these image? Because we don’t use a version tag at all. We always use :latest image avaiable
DietPi-Software
─────────────────────────────────────────────────────
Step: Installing Portainer: Simplifies container management in Docker (standalone host)
[ OK ] DietPi-Software | docker volume create portainer_data
[ INFO ] DietPi-Software | Portainer will be deployed now. This could take a while...
[ INFO ] DietPi-Software | docker run -d -p 9002:9000 --name=portainer --restart=always -v /run/docker.sock:/var/run/docker.sock -v /etc/ssl/certs/ca-certificates.crt:/etc/ssl/certs/ca-certificates.crt:ro -v portainer_data:/data portainer/portainer-ce, please wait...
Unable to find image 'portainer/portainer-ce:latest' locally
latest: Pulling from portainer/portainer-ce
Thats how it looks on my test VM. You see, no version tag on the image name.
root@DietPiVM:~# docker container ls -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
73fd754c24a9 portainer/portainer-ce "/portainer" 30 seconds ago Up 26 seconds 8000/tcp, 9443/tcp, 0.0.0.0:9002->9000/tcp, [::]:9002->9000/tcp portainer
root@DietPiVM:~#
You know that it will be revert on next DietPi release?
Anyway the initial issue is a different one because your image name is different than we install. Still open question, how did you install these image having a version tag?
@michapixel answering via email does not work, as we do not run an own email server .
Your changes to /boot/dietpi/dietpi-software will be reverted with every DietPi update. And indeed the question is how your Portainer image got this version tag. Did you update it manually in between, use watchtower or any such? We could change our install code to allow tags in the image, but then there could be potentially multiple images, and dietpi-software not removing the intended one. So safest is to only remove the one image that we also installed via dietpi-software, which does/should not have a version tag.