[dead]
Docker is deleting Open Source organisations - what you need to know
361–370 of 764 posts
Re: Docker is deleting Open Source organisations - what you need to know
#362Earlier quoted context omitted.
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.
In this case it is entirely planned work: Anyone depending on docker.io chose to make their processes dependent on online endpoints with whose operators you have no business relationship. An unpaid third-party service going offline should be far from unexpected and if you rely on it you better be ready to cope without notice. This is like complaining that you have to put out a fire because rather than fixing the spar…
> Anyone depending on docker.io chose to make their processes dependent on online endpoints with whose operators you have no business relationship.
This does not somehow make the work “planned”. That has a specific definition and this ain’t it.
Some people may have called it out as a risk when it was implemented. But that still doesn’t mean it’s planned.
Someone may have included an explicit report on how to deal with it at that time. That still doesn’t make it planned.
Also, just because it’s known to be a risk and may have a chance to happen in the future does not make it expected either. Nor planned.
Re: Docker is deleting Open Source organisations - what you need to know
#363Earlier quoted context omitted.
> And since podman doesn't have an official repo like docker, Hmm... https://github.com/containers/podman I found that on: https://podman.io/ so, I'm pretty sure it's official.
I meant a a repo for a distro package manager, so you can get the latest version regardless of whatever version your distro ships.
The most of major distros ship podman in their repositories. Just use your package manager to install podman.
Re: Docker is deleting Open Source organisations - what you need to know
#364Earlier quoted context omitted.
Are we not allowed to complain about unnecessary unplanned work being foisted on us with 30 days notice? That seems like an entirely relevant complaint for this forum but from your first reply, you’re acting like somehow it’s the greatest offense in the world that someone pointed this out.
Come on, 30 days notice is a walk in the park. Additionally, OP was the one complaining that changing a few URLs and eventually spinning up a new server. It's quite literally a one day or two job, unless you're at a company the size of Amazon (in which case, luckily for you, you're not the only SRE, so it's still just a few days). > The best I can come up with, at the moment, is waiting for each organization to make…
> Come on, 30 days notice is a walk in the park
Sure, maybe in a small business or startup, and even then I'd content not quite as easy as all that.
When you're dealing with anything larger, say involving multiple teams, organisations, and priorities, 30 days is an insanely short shrift to look at figuring out what your actual route forwards is (and if you're provisioning something new, making sure you're allowed to and have any relevant sign-offs etc.)
This particular situation with Docker doesn't affect us, but if it did this would have some serious knock on implications. The teams in my org are already busy with things that need to GA by certain dates or there will be financial implications. It's not "tire fire" but in most cases it's solid "don't waste time" territory. There's always flex in the schedule, but the closer to a GA date you get the more rigid the schedule has to be.
Re: Docker is deleting Open Source organisations - what you need to know
#3651. I just started teaching myself Docker for my home server. How will this affect me?
2. What is a good alternative to Docker?
Thanks!
Re: Docker is deleting Open Source organisations - what you need to know
#366Earlier quoted context omitted.
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.
Are we not allowed to complain about unnecessary unplanned work being foisted on us with 30 days notice? That seems like an entirely relevant complaint for this forum but from your first reply, you’re acting like somehow it’s the greatest offense in the world that someone pointed this out.
It’s not like using cloud services without suitable contractual agreements isn’t a known risk?
Re: Docker is deleting Open Source organisations - what you need to know
#367Earlier quoted context omitted.
The SaaS part being the offering for creating developer.acme.com type pages?
No. Centralizing and sharing your API descriptions, test suites and plans, the various ad-hoc queries people usually keep in their notes or on Slack (and lose), handling involved auth stuff which is a hassle with curl, etc. I think they gravitate towards the same area as swagger.io or stoplight.io, but from the direction of using the existing APIs.
API schemas and test suites are usually stored as code in some sort of SCM. I googled "postman maven" and "postman gradle" and found nothing official so I guess they have nothing except stand-alone workspaces.
API registry is a useful tool with modern love for nanoservices when a team of five somehow manages ten of those but I don't see anything similar done by Postman. Two of the service registries I know of were implemented in-house for obvious reasons.
Re: Docker is deleting Open Source organisations - what you need to know
#368As I commented in yesterday's thread, this is not the first time Docker is pulling the plug on people with very short advance notice: See https://news.ycombinator.com/item?id=16665130 from 2018
Someone back then even wondered what would happen if such a change happened to Docker Hub https://news.ycombinator.com/item?id=16665340 and here we are today.
Re: Docker is deleting Open Source organisations - what you need to know
#369Earlier quoted context omitted.
Are we not allowed to complain about unnecessary unplanned work being foisted on us with 30 days notice? That seems like an entirely relevant complaint for this forum but from your first reply, you’re acting like somehow it’s the greatest offense in the world that someone pointed this out.
It’s not like using cloud services without suitable contractual agreements isn’t a known risk?
Sure. It’s a risk. But that doesn’t somehow make this work expected and planned, not invalidate the original comment.
It could have happened at any time. But it’s also been running for a decade now so there’s an expectation that things will continue rather than have the rug pulled with 30 days notice.
Re: Docker is deleting Open Source organisations - what you need to know
#370Earlier quoted context omitted.
>> Docker, the company, is failing. Docker, the container technology, is alive and very well. Is it though? Podman is more well liked (no daemon / non-root) and Kubernetes doesn't have direct support for it any more. I don't think it matters much that k8s uses CRI-O but docker needs to be #1 for running a container on a single machine. Yet, they seem to be letting that slip away because it is not directly monetizable…
> Is it though? Podman is more well liked (no daemon / non-root) and Kubernetes doesn't have direct support for it any more. I've used "Docker" as in "containerization", since they are often used synonymously and the grandparents intent was definitely to criticize the latter. Docker itself will quite likely stay around as a name, but I have no faith in the company.
The company has never been good though. The technology was great, but they never found a way to monetise it properly, and their whole approach to outreach, community, and developer experience was terrible. Their support, non-existent.
In fact, I'd go as far as to say that, given the ubiquity of their product, I can't think of a worse way a company could have performed. It's been about 10 years now since it really took off, and in that time, the technology has been great, but dealing with the company, always been difficult.