Cannot update Portainer

  • I have tried to update Portainer via the OMV GUI (Portainer --> Install)


    I get an error and now Portainer is not available anymore.

    Everything worked fine before i tried this


    - OMV7 on Asus Prime N100 -

    Snapraid on 2 Data drives & 1 Parity

    6.8 proxmox kernel

    • Official Post

    Try to remove it first and then install. If that doesn’t work remove Docker and then install it and Portainer.

    System Backup Typo alert: Under the Linux section the command should be sudo umount /dev/sda1 NOT sudo unmount /dev/sda1

    Backup Data Disk to Backup Disk on Same Machine: In a Scheduled Job:rsync -av --delete /srv/dev-disk-by-uuid-f8814ed9-9a5c-4e1c-8830-426968c20ea3/ /srv/dev-disk-by-uuid-e67439d5-00a3-4942-bd5f-b84ab86aa850/ Don't forget trailing slashes, and BE CAREFUL. (HT: Getting Started with OMV5)

    Equipment - Thinkserver TS140, NanoPi M4 (v.1), Odroid XU4 (Using DietPi): PiHole

  • Try to remove it first and then install. If that doesn’t work remove Docker and then install it and Portainer.

    I removed Portainer by OMV menu. That did not help. Result is the same.

    If i remove docker, will that not destroy my existing containers and config?




    I always use this for update of Portainer. Never had issues...


    https://documentation.portainer.io/v2.0/upgrade/upddocker/


    I tried this. Did not help:


    Code
    # docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always --pull=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce
    latest: Pulling from portainer/portainer-ce
    Digest: sha256:3e499846ae1830e9465de7f110cbf19f4dff076e80abc0f7a1d4b50e67c6b873
    Status: Image is up to date for portainer/portainer-ce:latest
    e30ffec6561eb24200c371fbf966e8f33e0d2851c9eb227b59909439bda39cb9
    docker: Error response from daemon: driver failed programming external connectivity on endpoint portainer (3674732e0dc620075ecca03dcd3bf15c637b32e39a1089ad8a07525fb8a77d78): Error starting userland proxy: listen tcp4 0.0.0.0:8000: bind: address already in use.



    Code
     netstat -pantu | grep 8000
    tcp        0      0 0.0.0.0:8000            0.0.0.0:*               LISTEN      31979/node

    - OMV7 on Asus Prime N100 -

    Snapraid on 2 Data drives & 1 Parity

    6.8 proxmox kernel

  • Ok i guess i found the cause. It seems that newer Portainer versions need a second port open on 8000.

    I have another application taking that port.

    I am now running portainer API on 8001 and it fired up.


    Works!

    - OMV7 on Asus Prime N100 -

    Snapraid on 2 Data drives & 1 Parity

    6.8 proxmox kernel

  • Seems like i have lost some of the config on the way.

    The docker-compose script for the only stack i have is gone.

    How could i recover that?

    - OMV7 on Asus Prime N100 -

    Snapraid on 2 Data drives & 1 Parity

    6.8 proxmox kernel

    • Official Post

    What version of OMV are you using?

    System Backup Typo alert: Under the Linux section the command should be sudo umount /dev/sda1 NOT sudo unmount /dev/sda1

    Backup Data Disk to Backup Disk on Same Machine: In a Scheduled Job:rsync -av --delete /srv/dev-disk-by-uuid-f8814ed9-9a5c-4e1c-8830-426968c20ea3/ /srv/dev-disk-by-uuid-e67439d5-00a3-4942-bd5f-b84ab86aa850/ Don't forget trailing slashes, and BE CAREFUL. (HT: Getting Started with OMV5)

    Equipment - Thinkserver TS140, NanoPi M4 (v.1), Odroid XU4 (Using DietPi): PiHole

  • monsen

    Added the Label OMV 5.x
  • Ok solved.


    Somehow i had non default location for the data volume on the host in my old Portainer installation. I reinstalled from commandline giving it the path to the old volume and now all config is there 8)

    - OMV7 on Asus Prime N100 -

    Snapraid on 2 Data drives & 1 Parity

    6.8 proxmox kernel

  • monsen

    Added the Label resolved

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!