Fix to a small issue with updating OCI docker images

[fabricionaweb]

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 Tuesday at 09:32 PM by fabricionaweb

[Simon]

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 Tuesday at 10:40 PM by Simon

[spyd4r]

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

[weirdcrap]

this fixed Recyclarr and PlexTraktSync for me, thanks!

[Sanjay]

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

[blaine07]

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)

[kaiguy]

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.

[kcgodwins]

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

[singularity098]

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!