4 ms·

Yes, good. After reading the comments on their image retention limits [0] talking about simply pulling the images all the time to keep them fresh, this seems li

Yes, good. After reading the comments on their image retention limits [0] talking about simply pulling the images all the time to keep them fresh, this seems like a reasonable response. I'll repeat what I wrote there [1]: If people really think this is a problem, they'd contribute a non-abusive solution. Writing cron jobs to pull periodically in order to artificially reset the timer is abusive. Non-abusive solutions include: - extending docker to introduce reproducible image builds - extending docker push and pull to allow discovery from different sources that use different protocols like IPFS, TahoeLAFS, or filesharing hosts I'm sure you can come up with more solutions that don't abuse the goodwill of people. ----------------------------- Additionally, hosting a local network docker repo would mitigate this rate limit completely. Or straight up pay. It's not that difficult. Getting mad about a free, open-source service becoming pay to use... I couldn't imagine the gall and conceitedness. 0: https://news.ycombinator.com/item?id=24143588 https://news.ycombinator.com/item?id=24143588 1: https://news.ycombinator.com/item?id=24144475 https://news.ycombinator.com/item?id=24144475

kortex 6y ago
> introduce reproducible image builds This is a great idea in concept, but in practice very challenging. RUN curl https://www.random.org/integers/?num=1&min=1&max=99999 https://www.random.org/integers/?num=1&min=1&max=99999 Docker will cache this after the first invocation. The build is not reproducible. Now what? Replace "curl random.org" with "nondeterministic and really expensive code build/model training/etc operation". > extending docker push and pull to allow discovery from different sources that use different protocols like IPFS, TahoeLAFS, or filesharing hosts This is great, if you can solve the image integrity/trust issues therein, which should be just some signing/merkle tree work.

kortex 6y ago

> introduce reproducible image builds This is a great idea in concept, but in practice very challenging. RUN curl https://www.random.org/integers/?num=1&min=1&max=99999 https://www.random.org/integers/?num=1&min=1&max=99999 Docker will cache this after the first invocation. The build is not reproducible. Now what? Replace "curl random.org" with "nondeterministic and really expensive code build/model training/etc operation". > extending docker push and pull to allow discovery from different sources that use different protocols like IPFS, TahoeLAFS, or filesharing hosts This is great, if you can solve the image integrity/trust issues therein, which should be just some signing/merkle tree work.