Issues getting started

[ehuizar1028]

I am using the getting started guide https://github.com/awslabs/soci-snapshotter/blob/main/docs/getting-started.md

Which seems to be working as intended. I do see an improvement when i run an image on that single node.

But if i navigate to a different node where i didnt perform the nerdctl pull/push commands described in this section push-an-image-to-your-registry , but i install SOCI and pull with the soci snapshotter, i receive unable to fetch SOCI index: unable to fetch descriptor AND mismatch content-length

Soci and lazy loading is a new concept to me so I may be missing something fundamental, but does anyone have any ideas on what's going on?

[Kern--]

Sounds like a bug.

mismatch content-length comes from the oras-go library which we use for fetching SOCI indexes. It happens when the size reported in the Content-Length header of the response doesn't match what we expect. This shouldn't happen because we go to the registry to get the size before we request the data.

Can you provide additional information? What registry are you pulling from? Can you reproduce it with other images (this would be especially helpful if you can reproduce it with a public image so we can try on our side)? Can you provide additional SOCI logs?

[Kern--]

Oh actually, this is goharbor/harbor#20187. Looks scheduled to release in v2.11

[Kern--]

Which was released 11 hours ago https://github.com/goharbor/harbor/releases/tag/v2.11.0 🎉

[ehuizar1028]

thank you! great timing then i guess! I have a dev instance i can update to 2.11 and will test and report back here.

Thanks Again!

[Kern--]

Awesome. Let us know if that doesn't fix it and we can keep looking.

[ehuizar1028]

confirmed, it works with v2.11!

Thanks Again!