If I try to update my Portainer Business Edition 2.19.2 to version 2.19.3 using the new methodology for upgrades, I get an error message:

update failed: server should have been restarted by the updater

​

https://preview.redd.it/n8v5mxpkkw1c1.png?width=274&format=png&auto=webp&s=f469a765a97528eeb9e9f123489ce8a94fec0678

https://preview.redd.it/gvv4iolikw1c1.png?width=444&format=png&auto=webp&s=2ca7b3b708b57b23c3e22da70af1eb2e10f44453

https://preview.redd.it/9153s0flkw1c1.png?width=323&format=png&auto=webp&s=b96609eceaaad53ef84958c96368ebb7294718a3

  • InformationOk2977@alien.topBEnglish
    1·
    11 months ago

    Same error for me, upgrading BE 2.19.1 -> 2.19.2 (skipped it) and 2.19.1 -> 2.19.3.

    Running on docker 24.0.7 standalone on ubuntu 22.04.3 LTS on WSL2 on Win11.

    From memory I had the same issue going from BE2.19.0 to 2.19.1 but it magically resolved itself when i restarted the container some how. /shrug

    • noffie-san@alien.topOPBEnglish
      1·
      11 months ago

      I had noticed that temporary container it created (and never deletes, BTW, so you’ll want to clean that up) but hadn’t thought to look at the logs. I’m seeing basically the exact same thing.

      2023/11/27 10:21AM INF portainer/portainer.go:76 > Updating Portainer on standalone environment | image=portainer/portainer-ee:latest 
2023/11/27 10:21AM INF dockerstandalone/update.go:28 > Starting update process | containerId=ef7fd725b19df3e07708d0a88ed1d5d2a699ea2707d78aae9ad99c44938162f7 image=portainer/portainer-ee:latest status=Pulling from portainer/portainer-ee id=latest status=Digest: sha256:0140cf5751b61d07bcd9b48a800f6e178bb114267d5d2be7c5f4770222651677 status=Status: Image is up to date for portainer/portainer-ee:latest 2023/11/27 10:21AM INF dockerstandalone/update.go:62 > Image is already up to date, shutting down | image=portainer/portainer-ee:latest containerId=ef7fd725b19df3e07708d0a88ed1d5d2a699ea2707d78aae9ad99c44938162f7