Vatoe

No expert here, but I would be eliminating that it is a hardware issue like faulty ram.

Okay, I have managed to fix this issue. Anyone who has this issue this should help. 1. Make a current backup of your flash drive (for the just in case scenario) 2. In unraid console remove the docker network database : rm /var/lib/docker/network/files/local-kv.db 3. Then restart the docker network: rm /var/lib/docker/network/files/local-kv.db After the restart br0 should now point to ipvlan. I am once again able to use a fixed ip address on br0 network for docker containers. Thanks to bmartino1 for chimming in. edit: you will need to re-create any custom networks and get your docker containers pointing to the relevant recreated networks. Some of my docker containers didnt restart so I had to reinstall the container with the 'newly' recreated network.

Good catch didn't notice that. I have unchecked the DHCP pool, and allowed custom network access, but the network still points to bridge (after server restart) unfortuntely. I check with the relevant docker container still the same error. I though there would have been some command line that could force or remap br0 to ipvlan. No luck on googling this point/issue so far.

I 'll watch the video when I get a chance, but to answer your question:

Long story short made changes to the cache drives on one of my unraid boxes. After the upgrade something happened and my br0 network and it now points to bridge rather than ipvlan. I have tried restarting the docker service etc, but it persists to pointing to this network. As a result there are 2 docker containers (the only two that require static ip, nearly everything else is on proxynet) I cannot set a static IP for via the Br0 as I get "Error response from daemon: Invalid address 192.168.1.17: It does not belong to any of this network's subnets." This used to work without issue. I have checked my other box and br0 does indeed point to ipvlan. Also while trying to research this issue, all the screenshots seem to point to the ipvlan for br0. Any help would be appreciated.

Still helping to this date with the fix! Still helping to this day. Thanks!

You're not alone. After working flawlessIy for months, I started get this error from time to time - there appears to be no rhyme or reason to it popping up. When it does appear it appears to hang around for weeks (the on battery message) - where I finally end up pulling out the cable. I have tried removing and reinstalling NUT drivers etc. Just this morning I popped the USB cable back in, and it now states that I'm 'online' rather than 'on battery'. I did try ignoring the on battery message, but my server randomly shut down (gracefully) a few times so I suspect the it was initiated as result of this on battery message.

Thanks for this container. Works a treat with 2 different Nvidia GPU cards. I swapped recently from Trex-Miner as it stopped working after the latest update. Gave this a try, and I am back up and running. Anyone here scratching their heads regarding the GPU settings when you have two installed, just put the ID of one only and both will be picked up and used. However, m just not sure of the path where it installed, as it not found in the appdata share and it doesnt seem to provide the option to instal in this share via the configuation settings - unless Im missing something...

Did you ever figure this out? I recently upgrade TREX and now have the same issue, after it working for 5 months without issue prior to the update.

Not sure how as I tried many things, but my issue seems to be resolved. I now suspect that my problems revolved around my internet service connecting out to the Community App store, not an unraid configuration issue.

I tried with with nginxproxymanager. I uninstalled it, but cant reinstall as I am getting the same error when trying reinstalling dockers from CA.

hey thanks for wading in. Force updates dont work. Some dockers showing that they are up to date and other not available status. See image. The majority have unavailable status though. When I try an update an 'available' one - it doesn't pull any data down but goes through the process quickly and then states; On the containers that are marked unavailable, the update process stalls for a while then it states; but remains unavailable after the 'force update'. cheers

Thanks for the suggestion. I hadn't noticed the bond setting. I have changed it, but unfortunately I still have the same issues. No issues with the docker image file. i think that setting was something I did a long time ago, as I don't even recall changing it to be honest. What is really weird that there is only one container that seems to download ( budge ) which was a random one I picked from CA. Every other docker I have tried will not download?

I can see from searches that this issue has come up from time to time, where the docker containers in Unraid show they are unavailable. My setup previous to last night (Sydney Australia time) has been working without issue for many months in its current form. I woke up to find that many of the dockers status were change to unavailable this morning. I have attempted all the cures in the previous threads and none of those worked. So I have; 1. changed the DNS settings to 1.1.1.1 and 1.0.0.1 (cloudflare dns servers) 2. I can ping an external ip address eg google.com 3. I have checked the status of the various services docker hub etc 4. SABnzb can download files 5. I cannot force update any of the containers, they just time out 6. I have restarted Unraid a number of times 7. The plugins page in Unraid seems to be ok - as they show the status of up-to-date (edit 1) I cannot install any new containers - managed to get a random contianer (budge) down but no others? (edit 2) this is the error reported when i try to reinstall nginxproxymanager " Error response from daemon: error parsing HTTP 408 response body: invalid character '<' looking for beginning of value: "<html><body><h1>408 Request Time-out</h1> Your browser didn't send a complete request in time. </body></html> ".See 'docker run --help'." (edit 3). Diagnostics attached as requested. Also during my attempting to diagnose the issue, I uninstalled nginxproxymanager with a view to reinstalling it. This is when I found out I coudnt download any further containers from CA. (edit 4) Also tried to remove the docker networks and restart the service, then recreate the networks I had (br0 and proxynet) via console using: rm /var/lib/docker/network/files/local-kv.db /etc/rc.d/rc.docker restart docker network create ***** Any help would be appreciated. This has me stumped. cheers darkmatter-diagnostics-20220218-0008.zip

Anyone who was having problems, ge the th GPU's to transcode? I tried a 1660 super and a 2060 super with no luck. All the settings/parameters were correct - tdarr continued to use CPU. edit: My issue was from it being mis-configured in the codec selection. I think maybe an update or something had the changed the settings as everything was working previously. The container had transcoded 8TB worth of files previously without issue.