wofo

That's what I thought originally, but you can actually use ` https://<your-bucket>.s3.amazonaws.com ` without Cloudfront or other service on top (it wasn't easy to find in th…

I tried using that API directly, but it unfortunately did require ordered uploads too :')

Yep, I originally thought that wouldn't work... But now I discovered (thanks to a comment here) that the registry is allowed to return an HTTP redirect instead of serving the layer blobs directly…

To be clear, the 8x was comparing the slowest ECR throughput measurement against the fastest S3 one. In any case, the improvement is significant.

Unfortunately, all the code is proprietary at the moment. If you are willing to get your hands dirty, the main thing to realize is that container layers are "just" tar files (see, for instan…

Indeed, they could support it through a non-standard API... I wish they did!

Ah, that's great! I'll have to look into it :)

I didn't expect that! It's a pity they don't expose an API for parallel uploads, for those of us who need to maximize throughput and don't mind using something non-standard.

That's true, unfortunately. I'm thinking about ways to somehow support private repos without introducing a proxy in between... Not sure if it will be possible.

The source code is proprietary, but it shouldn't take much work to replicate, fortunately (you just need to upload files at the right paths).

Indeed, you are free to push multiple layers in parallel. But when you have a 1 GiB layer full of AI/ML stuff you can feel the pain! (I just updated my original comment to make clear I'm tal…

Layers are fully independent of each other in the OCI spec (which makes them reusable). They are wired together through a separate manifest file that lists the layers of a specific image. It's a …

That's true, but I'd assume the server would like to double-check that the hashes are valid (for robustness / consistency)... That's something my little experiment doesn't do,…

I wonder whether the folks at Cloudflare could take the ideas from the blog post and create a high-performance serverless container registry based on R2. They could call it scrubs, for "serverles…

Other than backwards-compatibility, I can imagine simplicity being a reason. For instance, sequential pushing makes it easier to calculate the sha256 hash of the layer as it's being uploaded, wit…

No idea... I asked the same question here ( https://news.ycombinator.com/item?id=40943480 ) and am hoping we'll have a classic HN moment where someone who was involved in the desig…

Hi HN, author here. If anyone knows why layer pushes need to be sequential in the OCI specification, please tell! Is it merely a historical accident, or is there some hidden rationale behind it? Edit:…