Hello,
do I have to update portainer exclusively with “dietpi-software reinstall 185”?
I accidentally tried an update in portainer itself with recreate. (with watchtower)
This obviously did not work properly - the image is marked as follows.
> portainer/portainer-ce:<none>
Portainer itself is running but in portainer the reference to the update is unchanged:
“New version available 2.21.3”
Now I had tried again with “dietpi-software reinstall 185” - but that failed now.
How should I proceed - do I have to gut the Portainer container in Watchtower in the future
Can I run the update again cleanly?
can you share the whole output pls.
here the message:
WARNING: Concurrent execution of DietPi-Software detected
│
│ Please check if one of the following applies:
│ - This script already runs on another terminal/SSH session.
│ - Currently a cron or systemd background job executes the script.
│ - You started this script from within another DietPi program, causing a loop.
│
│ Please assure that the concurrent execution has finished, before retrying, otherwise cancel this instance.
│
│ The following info might help:
│ 563 root tty42 /opt/dietpi-dashboard/dietpi-dashboard
│ 11622 root pts/1 \_ /bin/bash /boot/dietpi/dietpi-software reinstall 185
│ 11665 root pts/1 \_ /bin/bash /boot/dietpi/dietpi-software reinstall 185
│ 11667 root pts/1 \_ grep -i dietpi
│ 7806 root tty1 \_ /bin/bash /boot/dietpi/dietpi-software reinstall 185
│ 11395 root tty1 \_ /bin/bash /boot/dietpi/dietpi-software reinstall 185
│ 11396 root tty1 \_ whiptail --title DietPi-Software --backtitle Virtual Machine (x86_64) |
│ IP: 192.168.178.34 | Use up/down buttons to scroll text --menu - Command: 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 - Exit code: 125 - DietPi version: v9.8.0 (MichaIng/master) | HW_MODEL: 20 | HW_ARCH: 10 |
│ DISTRO: 7 - Error log: Unable to find image 'portainer/portainer-ce:latest' locally latest: Pulling from
│ portainer/portainer-ce 2fdd3e02e7e5: Pulling fs layer 3745b0e5e59c: Pulling fs layer d40df14c1d7a: Pulling fs layer
│ 8215717c7c10: Pulling fs layer 542669febe7c: Pulling fs layer 6c27c7f45b54: Pulling fs layer 8acaeb74c182: Pulling
│ fs layer 542669febe7c: Waiting 8215717c7c10: Waiting 6c27c7f45b54: Waiting c6e890230c95: Pulling fs layer
│ bb1e24a5d5a1: Pulling fs layer 4350eaf0c914: Pulling fs layer 4f4fb700ef54: Pulling fs layer 8acaeb74c182: Waiting
│ c6e890230c95: Waiting bb1e24a5d5a1: Waiting 4350eaf0c914: Waiting 4f4fb700ef54: Waiting 3745b0e5e59c: Verifying
│ Checksum 3745b0e5e59c: Download complete 2fdd3e02e7e5: Verifying Checksum 2fdd3e02e7e5: Download complete
│ 2fdd3e02e7e5: Pull complete 3745b0e5e59c: Pull complete d40df14c1d7a: Verifying Checksum d40df14c1d7a: Download
There is an installation already running. Looks like from inside the dashboard. Probably you closed the browser?
sorry - here again:
- Command: 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
│ - Exit code: 125
│ - DietPi version: v9.8.0 (MichaIng/master) | HW_MODEL: 20 | HW_ARCH: 10 | DISTRO: 7
│ - Error log:
│ **Unable to find image 'portainer/portainer-ce:latest' locally**
│ latest: Pulling from portainer/portainer-ce
│ 2fdd3e02e7e5: Pulling fs layer
│ 3745b0e5e59c: Pulling fs layer
│ d40df14c1d7a: Pulling fs layer
│ 8215717c7c10: Pulling fs layer
│ 542669febe7c: Pulling fs layer
│ 6c27c7f45b54: Pulling fs layer
│ 8acaeb74c182: Pulling fs layer
│ c6e890230c95: Pulling fs layer
│ bb1e24a5d5a1: Pulling fs layer
│ 4350eaf0c914: Pulling fs layer
│ 4f4fb700ef54: Pulling fs layer
│ 8acaeb74c182: Waiting
│ c6e890230c95: Waiting
│ bb1e24a5d5a1: Waiting
│ 4350eaf0c914: Waiting
│ 8215717c7c10: Waiting
│ 542669febe7c: Waiting
│ 6c27c7f45b54: Waiting
c6e890230c95: Verifying Checksum
│ c6e890230c95: Download complete
│ bb1e24a5d5a1: Verifying Checksum
│ bb1e24a5d5a1: Download complete
│ 4350eaf0c914: Verifying Checksum
│ 4350eaf0c914: Download complete
│ d40df14c1d7a: Pull complete
│ 4f4fb700ef54: Verifying Checksum
│ 4f4fb700ef54: Download complete
│ 8215717c7c10: Pull complete
│ 542669febe7c: Pull complete
│ 6c27c7f45b54: Pull complete
│ 8acaeb74c182: Pull complete
│ c6e890230c95: Pull complete
│ bb1e24a5d5a1: Pull complete
│ 4350eaf0c914: Pull complete
│ 4f4fb700ef54: Pull complete
│ Digest: sha256:ff9ac3a6e57fb94a489bd3cc02bb0da3887cb2aa6ddbde3e429b1da2bd5826d5
│ Status: Downloaded newer image for portainer/portainer-ce:latest
│ docker: Error response from daemon: Conflict. The container name "/portainer" is already in use by container
│ "f526d3541b71de8350fd2f7837c5ef45e8246e785eadcb43f136ec7db50e1712". You have to remove (or rename) that container
you would need to drop the container created by Watchtower first. Afterwards it should be possible to restart with our DietPi script.
thanks
How can I update in the future?
should i uninstall watchtower, or is there a possibility to update to latest?
This should update to latest image available. I don’t think there is a need to use Watchtower