Hacker News new | ask | show | jobs
by nirui 1841 days ago
Sad. I was hoping for multi-arch support (for Free tier, I don't make money out of my opensource image), and got this instead.

I wish the company could eventually found a way to make more money. Kubernetes too heavy to run, while Docker Swarm is rather reasonable. I guess there is a market gap?(???)

3 comments

It's hard to make more money if all people expect is more free service.
I see the dilemma there.

Most people I know of treats Docker.com as some kind of infrastructural service, it's like GitHub/GitHub Action+a Package Manager (Registry). For those who use these kind of service, they're expecting some kind of advanced (feature rich) free package for individuals, and a more advanced version for people who makes money out of the image/product they uploaded.

So, I think the nature of the service environment basically determined that most people who use Docker Cloud will end up be a free tier users. I guess this is something needs to be cracked by Docker Inc.

If you learn to program with Node.js, one chapter of your tutorial will be to show that NPM is "THE repository for Node packages".

For me, it is part of what makes some of these technologies leaders of what they do. If Node.js has NPM; Rust has Crates.io; and Debian has their repos, why wouldn't Docker have DockerHub? From my POV of 100% user of these technologies, it just seems natural (or at least that's just what they have made us to expect).

Actually what doesn't seem natural is if NPM suddenly deleted old package versions just mere months after they didn't get any download. I know we're talking about containers, which take more disk space than a NPM package... but still, that policy change from Docker Hub felt odd. Now we have to worry about regularly refresh the containers we care about.

(regarding the mantra "you should rebuild them anyway", well, when you want to reproduce a bug, you don't need to rebuild old packages in other repositories, right?)

GitHub's Container Registry has multi-platform support, and I haven't encountered any limits. I believe the same is true of Google's Container Registry. There's not much reason to sacrifice features to use Docker's own registry.
I started using Docker hub recently and I can't avoid to say how outdated it feels. I just use it because is the default thing.

Every other registry I've tried works better.

While it's a managed service with all the lock-in that goes with, but ECS seems to be a nice sweet spot of what you need from Kubernetes without the complexity.

Hashicorp Nomad is an open-source option.