Comment by nickjj
6 years ago
The FAQ[0] says pulling an image once every 6 months will prevent it from being purged by resetting the timer.
It doesn't seem like a big deal really. It just means old public images from years ago that haven't been pulled or pushed to will get removed.
This may not be a big deal for small-time projects. But does this mean e.g., the official Node images for older runtime versions could disappear? I recently needed to revive an app that specifically required node:8.9.4-wheezy, pushed 2 years ago. An image that specific and old will quite possibly hit 0 downloads per 6 months in short order, if it hasn't already.
That is a really good point. I wonder if official images will be treated differently.
(I work for Docker). Inactive official images will not be deleted. We are updating the FAQ shortly.
looks like there will be some bots that pull images on a periodic basis cropping up
Why not just pay this 60$/year? I mean if it's something important then it's worth paying for. If not - there is cheaper storage available when one can archive their containers.
Everyone should just start using Googles Cloud Build service IMO, it will cost you pennies. You can literally just do a `docker build -t gcr.io/project/image:0.0.1` and it will automatically tar up and send your build directly to their build service and create the container. It's about the cheapest and easiest build service I've seen.
https://cloud.google.com/cloud-build
3 replies →
Not a lot of money for a viable company, but it might be prohibitive if you're the main contributor to a smaller open source project, and that money will have to come out of your own pocket.
I agree it’s probably better to just pay, but certainly if it’s that cheap to circumvent then people will do it to save $60
Yep, everybody will have a small scheduled Github Action pulling their image once per month or similar ¯\_(ツ)_/¯