(no title)
Tomdarkness | 5 years ago
Guess this would work out okay for storing some development images but definitely does not seem feasible for production use.
Unless I'm missing something? There's some fine print about it being free within the context of a github action, but this doesn't really seem clear. Does my fleet of ec2 instances pulling down the image after a new deployment count as within an "action"?
clarkbw|5 years ago
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.
waheoo|5 years ago
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?
Leo_Verto|5 years ago
imunolion|5 years ago
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?
tilolebo|5 years ago
avery42|5 years ago
judge2020|5 years ago
luhn|5 years ago
Edit: Found it. https://github.com/features/packages#pricing