We recommend using GHCR for the development and test workflows and then publishing to the "Cloud *CRs" for your production images such that they can be pulled directly from there.
We recommend using GHCR for the development and test workflows and then publishing to the "Cloud *CRs" for your production images such that they can be pulled directly from there.
Because that's how you get paid or is there actually a value add here I'm not seeing?
"Tighter integration" and stronger vendor lockin isn't actually a selling point for anyone but the seller.
I'm not sure I buy the "better reproducibility" line either, whats better here?
As mentioned, this is best (for now) as a dev/test tool, rather than a general container registry.
Disclosure: I work at Azure.
Disclosure: that was obvious :)
No hard feelings, just pointing out the community needs more than corp speak to be convinced, especially when Microsoft is telling you "its just better ok"
The problem is, tighter coupling still comes with costs that some people aren't willing to pay.
I have 2GB container image, originally pulling takes 31-44sec. After migrating to ghcr.io, it was 38sec. Image is set public and running on a private(org) repository Action.
How much faster should we expect?