Live data from Hacker News

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

blog.alexellis.io

521–530 of 764 posts

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

#521

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…

Why not use your own registry with a pull-through cache?

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

#522

Earlier quoted context omitted.

Does Nix have an equivalent of docker-compose yet? nix-shell is amazing for installing binaries, but actually wiring up and running the services doesn't seem like a solved problem. Unless Nix expects a separate tool to do this once binaries are installed, of course.

https://github.com/hercules-ci/arion which allow docker-compose

oooh, I did not know of this, nice!

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

#523

Earlier quoted context omitted.

While that's true, for the amount of network traffic they're likely moving around, I wonder where they're placing their servers. eg something like AWS with massive data transfer costs, vs something else like carefully placed dedicated/colocation servers at places which don't charge for bandwidth

If it's AWS, they've surely got a huge discount. No way they're paying 8+x normal big-fish CDN rates for transfer. At their scale, it would have easily been worth the effort to move to something cheaper than AWS long ago, or else to negotiate a far lower rate.

It is on S3.

    keeb@hancock > [/home/keeb] dig +short hub.docker.com
    elb-default.us-east-1.aws.dckr.io.
    prodextdefblue-1cc5ls33lft-b42d79a68e9f190c.elb.us-east-1.amazonaws.com.

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

#524

> Start publishing images to GitHub And when GitHub starts similar shenanigans, move out to where? I am old enough to know the we can't trust BigTech and their unpredictable behaviors. Eventually we need to start a Codeberg like alternative using Prototype funds to be self reliant. 1: https://codeberg.org/ 2: https://prototypefund.de/

> And when GitHub starts similar shenanigans The difference between GitHub and Docker is that GitHub is profitable.

So is Docker Inc. The last I heard it is profitable and is doing quite well

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

#525

> Start publishing images to GitHub And when GitHub starts similar shenanigans, move out to where? I am old enough to know the we can't trust BigTech and their unpredictable behaviors. Eventually we need to start a Codeberg like alternative using Prototype funds to be self reliant. 1: https://codeberg.org/ 2: https://prototypefund.de/

Codeburg is more strict for blocking projects at the moment. Wikiless is blocked by Codeburg for using the Wikipedia puzzle logo but is still up and unchanged on GitHub.

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

#526
post #477

Earlier quoted context omitted.

> If those images disappear, we lose the ability to release and that's not acceptable. This shines light on why it is so risky (from both availability and security perspectives) to be dependent on any third party for the build pipeline of a product. I have always insisted that all dependencies must be pulled from a local source even if the ultimate origin is upstream. I am continuously surprised how many groups simpl…

Likewise. I've always insisted on building from in-house copies of external dependencies for precisely this kind of scenario. It astonishes me the number of people who didn't get why. Having things like docker rate-limiting/shutdowns, regular supply chain attacks, etc has been helping though. Slightly related: actually knowing for sure that you've got a handle on all of the external dependencies is sometimes harder t…

> Building in an environment with no outbound network access turns up all sorts of terrible things

Yes, highly recommended to build on such a system, it'll shake out the roaches that lie hidden.

In a small startup environment, the very least to do is at least keep a local repository of all external dependencies and build off that, so that if a third party goes offline or deletes what you needed you're still good.

For larger enterprises with more resources, best is to build everything from source code kept in local repositories and do those builds, as you say, in machines with no network connectivity. That way you are guaranteed that the every bit of code in your product can be (re)built from source even far in the future.

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

#527

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…

Time for you to locally clone the dockerfiles you're reliant on, build up your own in house repository, and then do what has been done since time immemorial.

Mirror the important shit. No excuses, just do. Yes, it's work. I guarantee though, you'll be less exposed to externally created drama.

Making sure your org stays up to date though, that's on you.

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

#528

Docker 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.

Yes, even when it was launched was obvious because used they packaged and configured existing solutions. It was like a company behind 'ls' (irony).

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

#529

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 probably wanna move to AWS Public ECR Gallery. They have a notion of official images.

AWS is in a better position to offer long term coverage.

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

#530

Earlier quoted context omitted.

except you cant deploy Nix files, and even if you could, better be sure that every employee is using Nix and have the same configuration. The whole point of docker is to make reproducible builds everywhere, not just your computer.

> except you cant deploy Nix files NixOps and nix-deploy: EXIST! https://arista.my.site.com/AristaCommunity/s/article/Deploy-... > better be sure that every employee is using Nix and have the same configuration. The whole point of docker is to make reproducible builds everywhere, not just your computer. lol, "tell me you never used Nix without telling me you never used Nix" because it literally guarantees that , each…

First you are tightly coupling your CI to your developers machine, that in itself is already a pretty bad idea. Second, if one employee wants to install htop on their machine, then every employee will have to install it, this can quickly become a problem when you have 500+ developers. Third, I think you missed the first part on the second quote, you are FORCING every developer to not only use linux but also to use one distribution that is pretty niche.
Post reply on HN