Earlier quoted context omitted.
I think they potentially could have made a decent business out of it but they made a lot of bad business decisions. I find myself shaking my head at a lot of their technical decisions too. Podman seems to me to be a case study for how to do this right.
Podman is interesting. I like the architecture problems it solves with respect to Docker but the way they went about it was typical big business Red Hat. Dan Walsh, Podman's BDFL it seems, basically stood in front of RHEL / OpenShift customers for years bashing Docker even when a majority of the things he was claiming were less than half baked. RHEL made sly moves like not supporting the Docker runtime, even at a tim…
Docker is deleting Open Source organisations - what you need to know
311–320 of 764 posts
Re: Docker is deleting Open Source organisations - what you need to know
#312Earlier quoted context omitted.
Docker should have been a neat tool made by one enthusiast, just like curl is. Instead it has a multi-million dollar company behind it, and VC's who demand profits from a thing that shouldn't have ever had a business plan.
> Instead it has a multi-million dollar company behind it, and VC's who demand profits from a thing that shouldn't have ever had a business plan. But you don't have to host curl? Who's gonna put the money to host all the images and bandwidths that ten of thousands of companies use but never pay?
Re: Docker is deleting Open Source organisations - what you need to know
#313Earlier quoted context omitted.
I'm assuming creative calculations. Like Uber's idea of "earnings" changed when they went public.
Based on what? How is that more likely than just them being able to finally generate revenue, considering they started focusing on that a few years ago? I don't get your comment at all
Re: Docker is deleting Open Source organisations - what you need to know
#314Docker the tool has been a massive benefit to software development, every now and then I have a moan about the hassle of getting something bootstrapped to run on Docker, but it's still worlds better than the old ways of managing dependencies and making sure everyone on a project is aligned on what versions of things are installed. Unfortunately Docker the company appears to be dying, this is the latest in a long line…
I must be missing something obvious, because otherwise I feel like I'm going insane.
Re: Docker is deleting Open Source organisations - what you need to know
#315Docker the tool has been a massive benefit to software development, every now and then I have a moan about the hassle of getting something bootstrapped to run on Docker, but it's still worlds better than the old ways of managing dependencies and making sure everyone on a project is aligned on what versions of things are installed. Unfortunately Docker the company appears to be dying, this is the latest in a long line…
Docker should have been a neat tool made by one enthusiast, just like curl is. Instead it has a multi-million dollar company behind it, and VC's who demand profits from a thing that shouldn't have ever had a business plan.
Re: Docker is deleting Open Source organisations - what you need to know
#316Earlier quoted context omitted.
That’s unplanned work. There’s other work needing to be done as well.
And a sudden fire is also unplanned work, but that's still your work. If this is such a threat, then maybe shift priorities around.
Re: Docker is deleting Open Source organisations - what you need to know
#317Earlier quoted context omitted.
You should be escrowing any Docker images you depend on, I'd have thought.
Good thing is that setting up an image registry in AWS is so simple! (Ha-ha, only serious.)
Re: Docker is deleting Open Source organisations - what you need to know
#318Earlier quoted context omitted.
You're right, it's both easier and simpler since no daemons are involved. podman-compose has the same command-line interface and has worked ok for me so far (maybe 3 or 4 years at this point).
Podman-compose isn't fully compatible with the new compose spec. Also I really don't care if docker has a daemon or not, for me it offers feature like auto starting containers without bothering with SystemD, and auto updates using watchtower and the docker socket. And since podman doesn't have an official distro package repo like docker, you are stuck use whatever old version shipped in your distro without recent imp…
Hmm... https://github.com/containers/podman
I found that on: https://podman.io/ so, I'm pretty sure it's official.
Re: Docker is deleting Open Source organisations - what you need to know
#319Docker the tool has been a massive benefit to software development, every now and then I have a moan about the hassle of getting something bootstrapped to run on Docker, but it's still worlds better than the old ways of managing dependencies and making sure everyone on a project is aligned on what versions of things are installed. Unfortunately Docker the company appears to be dying, this is the latest in a long line…
Docker should have been a neat tool made by one enthusiast, just like curl is. Instead it has a multi-million dollar company behind it, and VC's who demand profits from a thing that shouldn't have ever had a business plan.
Bandwidth and storage is not ultimately not free, it has to be paid for.
Re: Docker is deleting Open Source organisations - what you need to know
#320As an SRE Manager, this is causing me a hell of a headache this morning. In 30 days a bunch of images we depend on may just disappear. We mostly depend on images from relatively large organizations (`alpine`, `node`, `golang`, etc), so one would want to believe that we'll be fine - they're all either in the open source program or will pay. But I can't hang my hat on that. If those images disappear, we lose the abilit…
Or you could, you know, host a Docker registry and reupload those images to something you control. Worst case scenario, in 30 days, nothing is gone from Docker and you can just spin it down. Your job as an SRE is not to look at things and go "oh well, nothing we can do lol".
Some of those charts will not have variables that let you override the docker images and tags, so some of those will not be usable without creating a new release.
This is one of the primary reasons to vendor your third party docker images into a docker registry that you control.