Bintray issue?

  • I just tried an apt update on my OMV4 system and there are these errors:


    Code
    Ign:19 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker stretch InRelease
    Err:20 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch Release
    502  Bad Gateway
    Err:21 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing stretch Release
    502  Bad Gateway
    Err:22 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker stretch Release
    502  Bad Gateway


    This was happening yesterday and still today. When I searched the forum, it looks like this has happened a few times before. Can I change those to non-bintray repositories?


    I've been thinking of upgrading to OMV6 but I've been waiting until it's released. In the meantime, I wanted to update everything before I make a complete backup. I made a backup before starting the updates too.


    Can someone follow-up with bintray? I think that happened in one of the previous times it was having issues.


    Thanks

    • Official Post
  • If you are planning to do a fresh install, maybe do this right now with omv6. The upgrade from 4 to 5 to 6 may be painful.

    A fresh install is easy, if you do not have many users / groups set up or are running things beside omv.


    The way docker is configured changes significantly between 4 and 5 and some plugins got abandoned.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • Thanks macom. I searched for bintray but for some reason, that one didn't come up. I just tried the search again and sure enough it was the first item returned. One thing it did was jump to a specific post in the thread and skipped the text at the top about OMV4. More likely reason was I was having one of those days and I couldn't read straight...


    I'm in the same boat as the other person. My OMV4 setup is working fine and I have everything in docker.


    If I upgrade to OMV6, I'll have to install the most recent Armbian version (Bullseye), OMV6 and then re-setup each docker. That's going to be a real pain. I've also customized a few other items which I'll have to redo and worse...remember what I did :) I have most of it documented in my Wiki but there's always a few items that either weren't documented or some steps were missed. Maybe I'll try to set it up separately on another SBC I have laying around.


    Zoki, I'd like to upgrade to the most recent. I have my docker containers/images on a data drive. I was hoping to just upgrade docker and keep using those dockers items or run some update process on them, if possible. I know that docker changed in OMV. It's mostly done through Portainer now, which I've also installed. In any case, I think I'll just do the OMV4 upgrade for now and will rethink after OMV6 is final.


    The update now works without errors. Thanks again.

  • If I upgrade to OMV6, I'll have to install the most recent Armbian version (Bullseye), OMV6 and then re-setup each docker

    I'm not a docker upgrade expert, but to my understanding the (docker) containers (and their state) are just saved on disk and need to be restarted after any upgrade. I seem to remember a "how to" and some forum posts on this topic. Did you search for this topic?

    omv 6.9.6-2 (Shaitan) on RPi CM4/4GB with 64bit Kernel 6.1.21-v8+

    2x 6TB 3.5'' HDDs (CMR) formatted with ext4 via 2port PCIe SATA card with ASM1061R chipset providing hardware supported RAID1


    omv 6.9.3-1 (Shaitan) on RPi4/4GB with 32bit Kernel 5.10.63 and WittyPi 3 V2 RTC HAT

    2x 3TB 3.5'' HDDs (CMR) formatted with ext4 in Icy Box IB-RD3662-C31 / hardware supported RAID1

    For Read/Write performance of SMB shares hosted on this hardware see forum here

  • This heavily depends where the data is stored, how directories are referenced and how/where the docker container definitions are stored.


    Worst case (most work) is if the docker root directory is on the os disk, directories are referenced with absolute /media/... or /srv/dev-disk-by-label... and container have been created just by command line or a no longer existing ui.


    If you tell us more, I may be able to help.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • In OMV4, the docker "plugin" has a setting for the docker base path. I changed it to my os-data drive before setting up all of my docker stuff. I think all of my images, containers, volumes, etc are all on this drive.


    So, it's not my os/system drive but not what I consider my data drive(s) either, if that makes sense. It's an NVME drive I use for docker and used by all of my docker containers for config and other items.

  • This is ok, as only the os disk gets overwritten by a fresh install. So what you need to do is (after installing OMV6) set the same path in the UI, hit save and then install docker.

    This should give you all services back in the state you left them in OMV4.

    If I remember correctly OMV had a management interface for containers. This does no longer exist. Take a screenshot, so you can recreate the corresponding containers by a means of your choice.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • OMV had a management interface for containers. This does no longer exist. Take a screenshot,

    in addition to screenshot having a copy of config.xml database file (located in /etc/openmediavault)may be required
    see https://openmediavault.readthe…ighlight=xml#how-it-works

    a quick view of docker config can be obtained by running below bash commands:

    Code
    cat /etc/openmediavault/config.xml | grep docker

    omv 6.9.6-2 (Shaitan) on RPi CM4/4GB with 64bit Kernel 6.1.21-v8+

    2x 6TB 3.5'' HDDs (CMR) formatted with ext4 via 2port PCIe SATA card with ASM1061R chipset providing hardware supported RAID1


    omv 6.9.3-1 (Shaitan) on RPi4/4GB with 32bit Kernel 5.10.63 and WittyPi 3 V2 RTC HAT

    2x 3TB 3.5'' HDDs (CMR) formatted with ext4 in Icy Box IB-RD3662-C31 / hardware supported RAID1

    For Read/Write performance of SMB shares hosted on this hardware see forum here

Participate now!

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