Portainer from OMV4 to OMV5

    • OMV 5.x (beta)
    • Portainer from OMV4 to OMV5

      Hi all,

      i have a question about portainer and the switching from OMV4 to OMV5. When i use portainer in OMV4 for my Docker Container and all the settings with there, can i use it in OMV5 without reconfigurire all the options and settings for the container? I think on the easyest way, i start portainer in OMV5 and have all my Dockerfiles are running? Or is it more work ?(
      omv 4.x | 64 bit | omvextrasorg 4.x | kernel 4.16
      used plugins: nginx | mysql | docker-gui |rsnapshot | antivirus | apt tool | letsEncrypt |
      used other: netxtcloud | logitechmediaserver | Jellyfin | Lychee
    • i mean a new and clean OMV5 system with OMV-extras and portainer installation. Of course with all the sharedfolders from OMV4 and Docker
      omv 4.x | 64 bit | omvextrasorg 4.x | kernel 4.16
      used plugins: nginx | mysql | docker-gui |rsnapshot | antivirus | apt tool | letsEncrypt |
      used other: netxtcloud | logitechmediaserver | Jellyfin | Lychee

      The post was edited 1 time, last by happyreacer ().

    • Have not tried what you are planning to do, but here are my thoughts:

      Portainer is just a docker with a /data to store the Portainer data.
      Not sure what the status will be if you are using the same /data bind.

      If you used docker-compose inside Portainer to set up your docker and if you are using the same /data bind you will find all your docker-compose files and you can just run them.

      I am sure others will be interested to read your findings ;)
      Odroid HC2 - armbian - OMV5.x | Asrock Q1900DC-ITX - Intenso SSD 120GB - OMV5.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV5 Documentation - user guide :!:
    • docker is the same on OMV 4.x and 5.x. As long as the data-root is the same, the upgrade shouldn't make a difference.
      omv 5.2.4 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.2
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • My question is, are the settings of the individual containers, such as the included folders or options (TZ, PGID, PUID...) stored in the /data portainer folder? Specifically asked: I start only Portainer and have all my Docker containers running again?
      omv 4.x | 64 bit | omvextrasorg 4.x | kernel 4.16
      used plugins: nginx | mysql | docker-gui |rsnapshot | antivirus | apt tool | letsEncrypt |
      used other: netxtcloud | logitechmediaserver | Jellyfin | Lychee
    • happyreacer wrote:

      My question is, are the settings of the individual containers, such as the included folders or options (TZ, PGID, PUID...) stored in the /data portainer folder?
      The container settings should be stored in the folder you are using for docker. Otherwise, docker wouldn't know how to restart the container.

      happyreacer wrote:

      Specifically asked: I start only Portainer and have all my Docker containers running again?
      You shouldn't even have to start portainer. It is just another container.
      omv 5.2.4 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.2
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Thanks @ryecoaaron
      So that was a problem of understanding. I thought Porteiner is an administrative container for the other docker files. But that doesn't really make sense if I start a container into which I start again.
      omv 4.x | 64 bit | omvextrasorg 4.x | kernel 4.16
      used plugins: nginx | mysql | docker-gui |rsnapshot | antivirus | apt tool | letsEncrypt |
      used other: netxtcloud | logitechmediaserver | Jellyfin | Lychee