Live data from Hacker News

Docker is deleting Open Source organisations - what you need to know

blog.alexellis.io

411–420 of 764 posts

Re: Docker is deleting Open Source organisations - what you need to know

#411

As 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…

[deleted]

Re: Docker is deleting Open Source organisations - what you need to know

#412

As 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…

Many of the responses here are talking about how to vendor/cache images instead of depending on an online registry, but remember that you also need access to a supply chain for these images. Base images will continue to be patched/updated, and you need those to keep your own images up to date. Unless the suggestion is to build all images, from the bottom up, from scratch.

Re: Docker is deleting Open Source organisations - what you need to know

#413

Earlier quoted context omitted.

Some of it also sounds a bit like leftover angst from Red Hat winning the systemd war too. Turns out hanging out in someone else’s cathedral can have some pretty big benefits.

RedHat has not won any systemd war. From all the distributions out there using systemd, RedHat is the one that uses the least amount of systemd features. They are even going so far as disabling features. See * https://bugzilla.redhat.com/show_bug.cgi?id=1962257 * https://gitlab.com/redhat/centos-stream/rpms/systemd/-/blob/... Sometimes they even backport systemd features from more recent versions, disable them but le…

I too find Red Hat's poor documentation hygiene a pain in the arse. But as for the disabled system features, I think that they all fall into the category of experimental/unproven sort of features that overlap with other existing RHEL components. Every enabled feature has a cost in the form of support burden.

Re: Docker is deleting Open Source organisations - what you need to know

#414
post #330

As 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…

You can vendor images. Never have your product depend on something that is in the internet. Spin up Harbour locally and put it in the middle to cache at the very least.

Imagine if everyone actually did this. Then we would have a myriad of base images hiding even more malware than we do currently.

Not to mention vertically integrating the entire Docker layer set defeats the whole point of using Docker in the first place.

Re: Docker is deleting Open Source organisations - what you need to know

#415

Earlier quoted context omitted.

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…

If you're unable to take on a task that has a 30 day deadline in your org, regardless of size, you're experiencing a good amount of bloat.

Re: Docker is deleting Open Source organisations - what you need to know

#416

Earlier quoted context omitted.

> escrowing Are you sure this is what you mean? Escrow is a type of contactual arrangement, one type of which is agreeing with a commercial partner that you get a copy of their source-code if they go broke. I feel like you mean vendoring.

[flagged]

Maybe this is just me being a physicist, but I would have trouble applying the notion of escrow to anything that does not obey a law of conservation...

“Put that idea in escrow”—I assume I have to write it down first? “Put our incrementing page view count in escrow”—uh...? “Put my time in escrow”—how on earth am I going to get it back?

Similarly “escrowing your software dependencies”, hard to interpret if I didn't know the context. Whereas “vendoring” is similarly opaque but immediately recognizable as jargon and has made it into tools (`go mod vendor` and `deno vendor` for example).

Re: Docker is deleting Open Source organisations - what you need to know

#417
post #408

Earlier quoted context omitted.

"don't expect" or "for certain"? Can't really plan ahead without some kind of certainty.

There is no real distinction between those two phrases here, because the person using those phrases isn't ultimately in control.

Indeed. While I do maintain two of them, that maintenance is effectively equivalent to being an open source maintainer or open source contributor. I do not have any non-public knowledge about the Docker Official Images program. My interaction with the Docker Official Images program can be summed up as “my PRs to docker-library/official-images” (https://github.com/docker-library/official-images/pulls/TimW...) and the #docker-library IRC channel on Libera.Chat.

Re: Docker is deleting Open Source organisations - what you need to know

#418
post #313

Earlier quoted context omitted.

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

Based on observation of other companies. Fluffing your earnings isn't rare for private companies looking for investors.

[deleted]

Re: Docker is deleting Open Source organisations - what you need to know

#419

My first thought on this was good riddance. The dev model of "we've lost track of our dependencies so ship Ubuntu and a load of state" never sat well. However it looks like the main effect is going to be moving more of open source onto GitHub, aka under Microsoft's control, and the level of faith people have in Microsoft not destroying their competitor for profit is surreal.

>The dev model of "we've lost track of our dependencies so ship Ubuntu and a load of state" never sat well. This was my first thought when I learned of Docker. I have a hard time calling myself an 'Engineer' when there are so many unknowns, that I'm merely playing around until something works. I insist on being called a Programmer. It pays better than 'real' engineering. Why not embrace it? (Credit toward safety crit…

I remember back around 2009, our org had this horrible open source program, which shall not be named, foisted upon us by an excitable bloke who had heard wondrous things from the university where it had been developed. Well, we had a bitch of a time getting it running. Instructions and build scripts were minimal. We thrashed around.

I noted to someone that this felt less like a product and more like a website and set of scripts ripped from a working system. A few of us were shipped up to the originating university for a week to hob-knob with the people in charge of it. Toward the end, during the ritual inebriation phase, I managed to find out that they had never actually attempted to install it on a clean system. This had truly been ripped from a working system. And I thought to myself, "How horrible."

Now, I am admittedly pants at Linux. No good at all. But there is something about Docker and similar technologies that says, "Yes, we threw our hands in the air and stopped trying to make a decent installation system."

Re: Docker is deleting Open Source organisations - what you need to know

#420

As 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…

How hard is it to spin your own registry and clone those images there? I’m not heavily invested in my company’s infrastructure but as far as I can tell we have our own docker and npm registries
Post reply on HN