Compose plugin - black screen until the process is complete

  • After the latest update of the compose plugin, during a pull or up operation, a black screen appears in the terminal and remains until the process is complete. Up to that point, all previous activity is displayed, but there's no real-time information on what is currently being executed—instead, there's just a black screen.

    ASUS Prime N100I-D D4 | omv 7 | 64 bit | 6.1.0-31-amd64 kernel

    • New
    • Official Post

    I assume you are on OMV 7? What kind of system? (both good things to put in your signature by the way) Did you try ctrl-shift-R? I'm not seeing that on any of my omv docker systems. When the process is done, you see all info at that point?

    omv 7.7.0-2 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.1 | kvm 7.0.17 | compose 7.3.4 | 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!

  • both good things to put in your signature by the way

    Signature updated :)

    Did you try ctrl-shift-R?

    Yes i did and it doesn't change anything

    When the process is done, you see all info at that point?

    When the process is done, everything that was previously executed is displayed and as I mentioned earlier, this started after the last update of the compose plugin

    ASUS Prime N100I-D D4 | omv 7 | 64 bit | 6.1.0-31-amd64 kernel

    • New
    • Official Post

    When the process is done, everything that was previously executed is displayed and as I mentioned earlier, this started after the last update of the compose plugin

    I think I know what you are talking about now. My system just starts and stops containers fast enough that I didn't notice. Pretty sure it was this change which was done to show the error on the screen instead of creating the 500 error. I will see if I can go back to the older behavior while still displaying the error.

    omv 7.7.0-2 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.1 | kvm 7.0.17 | compose 7.3.4 | 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!

    • New
    • Official Post

    This should be fixed in next release - https://github.com/OpenMediaVa…4d78a5b66b9398a2ace0bced8

    omv 7.7.0-2 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.1 | kvm 7.0.17 | compose 7.3.4 | 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!

    • New
    • Official Post

    7.3.6 is in the repo.

    omv 7.7.0-2 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.1 | kvm 7.0.17 | compose 7.3.4 | 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!

  • reenstix

    Added the Label resolved
  • reenstix

    Added the Label OMV 7.x

Participate now!

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