ochagavia.nl

just_another_person , 3 days ago to technology in Using S3 as a container registry

I did this a few years ago for fun. It was a horrible idea, save for one singular use-case: tiny, few layers, single arch, and open-source.

The TLDR from my own experience: auth won’t work, complex images won’t work reliably, push won’t work, multiarch breaks, inspect breaks, meaning things like Helm won’t work, and most clients won’t work. Its basically just for show, and shouldn’t be done.

I’m sure I’m missing a few things, but for practical purposes, it’s not useful unless you’re using it for something hyper specific, at which point you may as well use the ‘export’ function to ship containers everywhere, which of course removes all the convenience of the container workflow.

Sure, it works, and maybe download speeds for the file are faster, but that’s it. Everything else is broken, and then you can’t simply do a “docker pull” to update again in the future.

admin , 3 days ago

Interesting summary, although not really an unexpected result.

Side note: I like your username.

sugar_in_your_tea , 2 days ago

If you’re considering S3, why not just use AWS’ container registry?