Hacker News new | ask | show | jobs
by chrisandchris 2141 days ago
It seems you simply have to pull it every 5.99 months to not get it removed. So add all your images into a bash script and pull them every couple weeks using crontab and you‘re fine.

On the other side, I see the need for making money and storage/services cannot be free (someone pays somewhere for it - always), but 6 months is not that much for specific usages.

2 comments

"Pulling docker images every 5 months as a service"
Hey, you could distribute that as a container on Docker hub...
Which would mean people will regularly pull it and thus prevent it from being deleted. I call that a self-sustainable business model.
This is both amusing and actually feasible
Finally a good use for that raspberry pi idling in the corner
How hard is it to pull non-ARM images from a pi?
You can pull another platform's image. If the image is only available for one platform, you can just pull it. If the image is available for multiple platforms, it will pull your platform instead, you need to explicitly specify the digest to get another platform's:

For example:

docker pull python@sha256:2d29705d82489bf999b57f9773282eecbcd54873d308a7e0da3adb8a2a6976af

Pulls the latest Python image for Linux Alpine running on IBM System/z.

Not what you were asking, but if you have qemu-user-static installed, you can even run Docker images for other platforms. For example:

docker run -it python@sha256:2d29705d82489bf999b57f9773282eecbcd54873d308a7e0da3adb8a2a6976af

That's Python for Linux for IBM System/z. Check the CPU architecture:

import os;os.uname().machine

Running other platform's images under QEMU is going to be quite slow on a Raspberry Pi, I imagine (I haven't tried it). But of course for this case you don't have to run the image, you just want to pull it, so that doesn't matter.

Just ensure you've busted the cache, otherwise you're only pulling a joke.
I'm sure you've cited research older than 5.99 months right?

I wish they would grandfather images before this new ToS to not get wiped so that future images would be uploaded to more stable and accepting platforms so images on Docker Hub from research pre-ToS update don't get wiped.

well it sounds like someone's gotta pony up the bucks for a their own image repo, rather than freeload off someone else's storage infra.
Full circle achieved.

START Run your own stuff on stuff you own. Run your stuff on other people's stuff you rent. This is too expensive to maintain at your rent. Pay us more. Back to run your own stuff on stuff you own. ...and so on, and so forth.

And this, ladies and gentlemen, is why anything worth doing is worth actually doing yourself. Nothing is worse than building something conditionally feasible on someone else only to have the rug pulled out from under you by sudden business pivots.

But that's the nature of the beast I suppose. I've certainly not found a great way to do it any other way.

Science Docker Repo as a Service backed by Amazon Glacier and index, one time fee to access?
Oh yes I did, some probably as old as myself. Things just don‘t change that much in certain areas.