How does the Docker story compare to NPM who are also freely hosting a bunch if stuff, heavily downloaded and relying on some paid users but mostly free. And NPM has “competing” repositorys too. Could the same happen with NPM where they need to charge? I get that NPM packages are smaller than docker images typically.
„npm enterprise“
You can run an in-house npm repository with that sold by Npm Inc.
I don’t know how sustainable it is but that’s probably one of their cash cows.
The narrative seems quite clear to me. They released the tooling and the services to become the defacto solution, and then Swarm was supposed to be the cashcow that turned that into cashflow. And then k8s happened. They've raised a tonne of capital, and it probably looked sane at the time. And now they're grasping at straws trying to figure out how else they can turn this into revenue. A lot of the recent narrative h…
> then Swarm was supposed to > be the cashcow that turned > that into cashflow. And then > k8s happened. We are still using Docker Swarm in production. It seems to be working fine so I always wondered why it never took off. But I am not a Devop. Can sb please give some insight on why kubernetes took off instead and why Dock Inc. failed with its cloud product?
Good question, I'm also interested in the answer. Probably has something to do with K8s being backed by Google, which has battle tested it in the form of their internal Borg infrastructure.
In its weird death spiral, if Docker Inc. were to be bought out by Microsoft, I shudder to think how much of the dev ecosystem would yet again depend on Microsoft's good graces to shoulder the burden of storage and data transfer costs for building products. They already do npm and Github (+ Github Container Registry) so they have some standing in being stewards in this space. On the plus side, it would perhaps give e…
> if Docker Inc. were to be bought out by Microsoft...
You can always use Podman. We already have fully OSS solutions in the container space.
I know I will get downvoted for this as off topic, but this is just the latest blog we've seen in this top 30 of many that show ZERO regard for legibility. Yes, I can zoom my browser, but c'mon. A 13px font for paragraph text is nearly hostile. It's not that legible to people with perfect eyesight, but then it's not at all legible to anyone with imperfect eyesight. It's like saying you don't care if anyone who reads…
At least on my Android in Chrome, it seems to have the same font size as hacker news. Requesting "Desktop Site" yields the same results. And yes, I do believe that Hacker News needs a bigger default font. (I'm getting old. You will too!)
My default zoom on HNews is 133%. I too am getting old (or my eyes are at least), and agree with you old sods :))
As a newcomer to the devops world I was kind of surprised at the general thesis of this article, that companies use docker hub and using something different is awkward. Neither of the two companies I’ve worked for use it (artifacory in both cases) and there is a general taboo around having docker desktop binaries on any company systems (though docker engine seems to be prevalent). I guess I had just assumed that the…
I have exactly the same experience. Can't imagine why someone'd use Dockerhub by default for enterprise use cases nowadays.
> Still, the point of this tangent about Docker Desktop is that Docker's decision to monetize via Desktop---and in a pretty irritating way that caused a great deal of heartburn to many software companies---was probably the first tangible sign that Docker Inc. is not the benevolent force that it had long seemed to be. Suddenly Docker, the open-source tool that made our work so much easier, had an ugly clash with capit…
> I'm not sure why they couldn't have been a bit more aggressive about monetization from the start? I'm not sure there is that much money in running a glorified specialized S3. Charging for disk space is terrible - the people who have money would probably just setup a private repo on S3 where it's cheaper and the people who don't aren't going to pay you. For the amount of money they raised I don't think that would ha…
Ofcourse there's money. Look at Dropbox, and the like.
> then Swarm was supposed to > be the cashcow that turned > that into cashflow. And then > k8s happened. We are still using Docker Swarm in production. It seems to be working fine so I always wondered why it never took off. But I am not a Devop. Can sb please give some insight on why kubernetes took off instead and why Dock Inc. failed with its cloud product?
Good question, I'm also interested in the answer. Probably has something to do with K8s being backed by Google, which has battle tested it in the form of their internal Borg infrastructure.
My understanding is that k8s was definitely never used internally at google (at least at the beginning). They may have learned some lessons from Borg, but k8s is very very much not Borg nor a Borg component. I remember lack of battle testing and architectural differences being a key criticism when k8s was released.
In its weird death spiral, if Docker Inc. were to be bought out by Microsoft, I shudder to think how much of the dev ecosystem would yet again depend on Microsoft's good graces to shoulder the burden of storage and data transfer costs for building products. They already do npm and Github (+ Github Container Registry) so they have some standing in being stewards in this space. On the plus side, it would perhaps give e…
> if Docker Inc. were to be bought out by Microsoft... You can always use Podman. We already have fully OSS solutions in the container space.
Where do you host the base images? Someone's footing that bill or are you paying for it?