34 minutes ago, kcgodwins said:

 

Thanks, I'll take a look at it.

 

Do you (or anyone) know why this has become an issue all of a sudden?  Just curious.

Thanks again.

Mike

What I've investigate so far, out of curiosity, and I may be wrong, cause I learned it today:

 

- although github registry works with both: Registry v2.2 and Open Container Initiative (OCI)

- seems like some Docker images are only with Open Container (and I dont know why or how this works), the webgui is sending the Accept header only for Registry 2.2 (see the docs)

- the changes in this thread is to add the Accept header for Open Container Initiative (see the docs)

That was my 2cents, hope it help to understand

Edited January 24, 20233 yr by fabricionaweb

1 hour ago, kcgodwins said:

 

Thanks, I'll take a look at it.

 

Do you (or anyone) know why this has become an issue all of a sudden?  Just curious.

Thanks again.

Mike

The submitted change in the GitHub PR shows that  additional manifest formats will now be accepted. The relevant documentation regarding the formats is in the code comments. Presumably some of the Docker projects have changed the format which was causing the original code to fail.

Edited January 24, 20233 yr by Simon

I was having issues with about 3 containers that would never go out of "not available". This did the trick.. thanks!

this fixed Recyclarr and PlexTraktSync for me, thanks!

Thanks for this fix!  Is this configuration persistent ?  or will have to do again after reboot ?

29 minutes ago, Sanjay said:

Thanks for this fix!  Is this configuration persistent ?  or will have to do again after reboot ?

Hey Sanjay,

 

please skim the contents and the Original Post. I think you’ll have no problem locating the answer. 🙂 

 

(No, it doesn’t survive Server Reboot)

Appreciate sharing this fix. I was getting this with one container, then a few days later another, and finally I had 5 containers with this issue. I was pulling my hair out thinking I had some issue with my DNS blocklists.

It was line 424 for v6.9.2; updated it and worked great.  Thanks all.

This fixed the issue for me as well!  The containers for Glances and Netdata were failing to check for updates until I did this.

 

Thank you!

Thx for this fix, its working perfect

On

On my server it was line 448

 

Made the changes as suggested.

 

I still get the error that the update for Virt-manager is unavailable.

 

So what now? Or better yet, since your update broke it, You fix it.

 

it seems every update I've installed for Unraid breaks something.

 

Where is your quality control?

Edited January 28, 20233 yr by Vetteman

53 minutes ago, Vetteman said:

I still get the error

 

53 minutes ago, Vetteman said:

since your update broke it

Seems to me that it was broken before the update

 

53 minutes ago, Vetteman said:

Where is your quality control?

really?

Edited January 29, 20233 yr by DarphBobo

 

HIGHLY recommended to NOT patch your docker files manually and instead use the plugin.  Patching manually means that if / when you update the OS to 6.12 any manually patches that you are applying automatically will potentially interfere with the OS and be a big pain to troubleshoot

I am not patching manually. I always use Unraid app to notify me of updates and install them.

 

I switched from Basic View in Apps to Advanced View as suggested in another thread, and the updates for Virt-manager appeared.

 

Sorry for getting upset, but today it was a bit stressful.

3 minutes ago, Vetteman said:

I am not patching manually. I always use Unraid app to notify me of updates and install them.

 

I switched from Basic View in Apps to Advanced View as suggested in another thread, and the updates for Virt-manager appeared.

 

Sorry for getting upset, but today it was a bit stressful.

The post about the plugin was not referencing you, but rather the community and everyone creating a script / manually patching the file.  Recipe for disaster since if / when you upgrade the OS you're going to forget that you were applying a patch manually via a script somewhere and now that patch is going to potentially cause problems whereas the plugin handles that occurrence correctly

49 minutes ago, Squid said:

The post about the plugin was not referencing you, but rather the community and everyone creating a script / manually patching the file.  Recipe for disaster since if / when you upgrade the OS you're going to forget that you were applying a patch manually via a script somewhere and now that patch is going to potentially cause problems whereas the plugin handles that occurrence correctly

So we should use the plugin for now and then can delete it once unraid is updated to 6.12?

The plugin will not install on 6.12+, so it's a install once, forget about it completely and you're safe going forward

16 hours ago, Squid said:

 

HIGHLY recommended to NOT patch your docker files manually and instead use the plugin.  Patching manually means that if / when you update the OS to 6.12 any manually patches that you are applying automatically will potentially interfere with the OS and be a big pain to troubleshoot

Doesn't show up for me in Community Apps.  I'm running 6.9.2.

@Squid just installed your patch, hit the "checking for updates" button and the annoying "not available" message is gone. I'm on Unraid 6.11.5 btw. Thanks for the script.

 

Just for understanding, this script will be autom. deleted / disabled when updating to OS 12.5? Means, no reason for being afraid of an upcoming update?

 

Regards

 

@Squid Thanks a lot , also fixed for me , found a lot :

(speedtest-tracker, PiAlert, 2fauth, crowdsec, GoAccess-NPM-Logs, changedetection.io, dashy, browserlesss, shwifty, Dozzle ....etc)

 

and the most strange thing they all worked befor ...

also checked https://github.com/limetech/webgui/issues/1111 and in next Unraid version this should be fixed .

On 1/29/2023 at 1:49 AM, Squid said:

 

HIGHLY recommended to NOT patch your docker files manually and instead use the plugin.  Patching manually means that if / when you update the OS to 6.12 any manually patches that you are applying automatically will potentially interfere with the OS and be a big pain to troubleshoot

 

I don't see this plugin in Community Apps. I'm on 6.9.2. Can it be manually installed from somewhere?

29 minutes ago, reverend remiel said:

 

I don't see this plugin in Community Apps. I'm on 6.9.2. Can it be manually installed from somewhere?

The plugin is set to only be installable on Unraid 6.11.x series.

1 hour ago, itimpi said:

The plugin is set to only be installable on Unraid 6.11.x series.

Okay, thanks. Manual patching it is, then.

On 1/29/2023 at 2:11 PM, Masterwishx said:

also checked https://github.com/limetech/webgui/issues/1111 and in next Unraid version this should be fixed .

Is there any regular cadence on unraid releases?  I've just started so wondering how long that might be since I've only got one docker not upgrading due to this.

1 hour ago, rkotara said:

Is there any regular cadence on unraid releases?  I've just started so wondering how long that might be since I've only got one docker not upgrading due to this.

No, that's why there's a plugin to patch it in the meantime.

Edited January 31, 20233 yr by Kilrah