All containers appear as "down" after update

  • All my docker containers appear as "down" after i updated OMV.

    They are although working fine as i can see in portainer.


    - OMV7 on Asus Prime N100 -

    Snapraid on 2 Data drives & 1 Parity

    6.8 proxmox kernel

    • Official Post

    What packages did you update? Just saying OMV was updated doesn't help much.

    omv 7.4.10-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.14 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    That shouldn't have affected the compose plugin. What if you click the Clear cache button on the Settings tab of the Compose plugin? Are the Containers and Stats tabs populated?

    omv 7.4.10-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.14 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Prolly nothing to do with anything.


    I did an update before, and it did update Docker... I rebooted and Docker did not restart, just a glitch as it happened once...Did you verify DOCKER itself is running?

    • Official Post

    I hit the clear cache button but that didn't have any effect.

    What about my other questions? Remember that I can't see anything on your system. Hard to help without info.

    omv 7.4.10-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.14 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • That shouldn't have affected the compose plugin. What if you click the Clear cache button on the Settings tab of the Compose plugin? Are the Containers and Stats tabs populated?

    Sorry.


    Containers and stats seem to be populated although i cannot tell if that is any different to before because i did not check.

    - OMV7 on Asus Prime N100 -

    Snapraid on 2 Data drives & 1 Parity

    6.8 proxmox kernel

    • Official Post

    If those tabs are working, then maybe there is something with your system that the plugin is not handling. Only way to know is to put your system in debug mode and visit the Files tab.


    sudo monit stop omv-engined

    sudo omv-engined -df


    # visit the files tab and look for errors in the omv-engined output

    omv 7.4.10-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.14 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Done that. No errors if i understand that right:


    - OMV7 on Asus Prime N100 -

    Snapraid on 2 Data drives & 1 Parity

    6.8 proxmox kernel

    • Official Post

    No errors if i understand that right:

    After you started debug mode, you went to the Files tab? There should be a lot more output.

    omv 7.4.10-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.14 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I assume you mean the files tab in the compose plugin? Sorry i just did not get what you meant:


    The log looks like there is an empty compose file somewhere. But i do not know where that is coming from. Maybe that is the problem?

    I manually checked all compose files and none of them is empty.

    • Official Post

    I assume you mean the files tab in the compose plugin? Sorry i just did not get what you meant:

    Yes. That is why I capitalized Files. And since we are working on a problem in the Compose plugin, I figured I didn't have to mention that.


    The log looks like there is an empty compose file somewhere. But i do not know where that is coming from. Maybe that is the problem?

    I manually checked all compose files and none of them is empty.

    It is saying the project name is empty. I ran into this in another thread and the version of docker-compose was very old. What is the output of:


    sudo omv-aptclean repos

    dpkg -l | grep docker

    omv 7.4.10-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.14 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Code
    root@debnas:~# dpkg -l | grep docker
    ii  docker                                           1.5-2                                      all          transitional package
    ii  docker-buildx-plugin                             0.12.1-1~debian.12~bookworm                amd64        Docker Buildx cli plugin.
    ii  docker-ce                                        5:25.0.3-1~debian.12~bookworm              amd64        Docker: the open-source application container engine
    ii  docker-ce-cli                                    5:25.0.3-1~debian.12~bookworm              amd64        Docker CLI: the open-source application container engine
    ii  docker-compose-plugin                            2.24.6-1~debian.12~bookworm                amd64        Docker Compose (V2) plugin for the Docker CLI.
    ii  python3-docker                                   5.0.3-1                                    all          Python 3 wrapper to access docker.io's control socket
    ii  wmdocker                                         1.5-2                                      amd64        System tray for KDE3/GNOME2 docklet applications
    • Official Post

    You must have disabled the docker repo a long time ago to have those versions. Re-enable the docker repo in omv-extras, run apt clean again, and then update your system. The old docker packages are causing this problem. I have added minimum version checks to the compose plugin in the last couple of days.

    omv 7.4.10-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.14 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • You are right, it is disabled. Weird. I don't think i did that. Maybe by mistake? ... strange


    This fixed it!! Thanks man

    - 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!