Latest Docker plugin update

    • Official Post

    I tried the apt clean button. Still looks the same.

    Not sure why then. The commit is here - https://github.com/OpenMediaVa…7ae25e6a567186e49f7f315c9 - and the 4.1.0 version in the repo has all commits.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    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

    For the future of docker, I found this: Cockpit

    I've been testing cockpit for months on my omv test VM. It doesn't seem to have any docker features that I can find. It is more for managing one or more machines. Maybe it has more features when running on redhat machines but it is pretty spares on Debian.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    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!

  • Not sure why then. The commit is here - https://github.com/OpenMediaVa…7ae25e6a567186e49f7f315c9 - and the 4.1.0 version in the repo has all commits.

    I checked the dates on the two files involved and they are dated yesterday so I know the 4.1 update took. And a year or so ago I patched those same two files with the same commits. Neither fix worked.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    • Official Post

    @Nefertiti Clear the browser cache

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    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!

  • @Nefertiti Clear the browser cache

    Does not work for me

    • Official Post

    Then try the apt clean button in omv-extras. If that doesnt work, you will have to remove the apiPort element from /etc/openmediavault/config.xml. If it is still there, I don’t understand why the code isn’t removing it.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    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!

  • Then try the apt clean button in omv-extras. If that doesnt work, you will have to remove the apiPort element from /etc/openmediavault/config.xml. If it is still there, I don’t understand why the code isn’t removing it.

    the button did nothing
    what part should I remove?
    <docker>
    <enabled>1</enabled>
    <apiPort>42005</apiPort>
    <version/>
    <versionInfo/>
    <sharedfolderref/>
    <dockermntent/>
    <uuid/>
    <orgpath/>
    <destpath/>
    <cwarn>1</cwarn>
    </docker>
    </services>
    </config>

  • I thought the problem was fixed, I did
    apt upgrade
    and got The property 'apiPort' does not exist in the model 'conf.service.docker'. in the GUI

    I solved it by remove openmediavault-docker-gui, docker-ce in cli, then update sources.list (apt update), install openmediavault-docker-gui 4.1

  • I see there’s a containerd.io update(1.2.0-1), anyone updated and can confirm it’s ok to run?

    OK here.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    • Official Post

    <apiPort>42005</apiPort>

    This line.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    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

    I see there’s a containerd.io update(1.2.0-1), anyone updated and can confirm it’s ok to run?

    It is installed by the docker package as a dependency. So, you don't have any choice.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    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!

  • Yep, for me the same. Did the update tonight and didn’t have any problems!


    Thanks again @ryecoaaron

    ----------------------------------------------------------------------------------
    openmediavault 6 | proxmox kernel | zfs | docker | kvm
    supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x10tb wd red | digital devices max s8
    ---------------------------------------------------------------------------------------------------------------------------------------

    • Official Post

    Is the update fixed? Can I update without risk?

    If you have a backup, your risk is greatly reduced. That said, most people are able to upgrade without issues. The other users have been able to have their problem solved fairly easily.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    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!

Participate now!

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