Live data from Hacker News

A new upstream project to break up Docker into independent components

github.com

91–100 of 321 posts

Re: A new upstream project to break up Docker into independent components

#91
post #75

Hi all, Docker founder here. It appears that the explanation in the pull request is not very clear. Sorry about that. We didn't expect the PR to be the first thing people read: there is a new website at mobyproject.org. Unfortunately Github is struggling under the load, and I can't update the PR text to clarify. Here is an updated version with some clarifications: Docker is transitioning all of its open source collab…

Very tangential: do you have any concerns about or plans to buy mobyproject.com? seems like its oscillating between parked domain and shady ads.

Re: A new upstream project to break up Docker into independent components

#92
post #91
post #75

Hi all, Docker founder here. It appears that the explanation in the pull request is not very clear. Sorry about that. We didn't expect the PR to be the first thing people read: there is a new website at mobyproject.org. Unfortunately Github is struggling under the load, and I can't update the PR text to clarify. Here is an updated version with some clarifications: Docker is transitioning all of its open source collab…

Very tangential: do you have any concerns about or plans to buy mobyproject.com? seems like its oscillating between parked domain and shady ads.

Thanks for the heads up, we'll look into getting that domain if we can.

Re: A new upstream project to break up Docker into independent components

#93
post #4

Earlier quoted context omitted.

It looks like they want to rename the OSS version, to differentiate it from their commercial version. They're using the analogy of Fedora->RHEL. Moby = open source development Docker CE = free product release based on Moby Docker EE = commercial product release based on Docker CE.

What exactly is the difference between Moby and Docker CE?

Docker Community Edition is the Docker you've always heard about, now with an Enterprise big brother (Docker EE).

Moby is a set of standardizable tools that underly that product which might be shared with OS suppliers, Kubernetes, or other virtualization solutions.

If you want containers for your apps, you want Docker. If you're bundling containerization components into your Linux distro/orchestration platform/custom hybrid cloud solution then Moby will be your swiss army knife :)

Re: A new upstream project to break up Docker into independent components

#94
post #75

Hi all, Docker founder here. It appears that the explanation in the pull request is not very clear. Sorry about that. We didn't expect the PR to be the first thing people read: there is a new website at mobyproject.org. Unfortunately Github is struggling under the load, and I can't update the PR text to clarify. Here is an updated version with some clarifications: Docker is transitioning all of its open source collab…

If moby is not a replacement for docker (your words), why does docker/docker redirect to moby/moby (your actions)?

Re: A new upstream project to break up Docker into independent components

#95
post #20

From comment by @stykes on the pull request: Moby = open source development Docker CE = free product release based on Moby Docker EE = commercial product release based on Docker CE. Nothing is dead; and everything that was open-source remains open-source. In fact we are open-sourcing new things.

So it's like Chromium, Google Chrome, and then imagine an enterprise version of Google Chrome?

Yes, that's a pretty good analogy. Except our "chromium" (Moby) actively encourages and facilitates creating completely different types of "browsers", not just Docker.

Re: A new upstream project to break up Docker into independent components

#97
post #56

What a horrible title. Docker isn't being renamed to Moby, but rather all of the open source components are being spun out into a new umbrella OSS org called Moby. No need to s/docker/moby anywhere. This is going to end up being a case study in how not to make announcements, because the news is otherwise big/interesting.

This url is redirecting so that has changed (a rather important url):

https://github.com/docker/docker

This all seems so unnecessary. Why didn't they just keep docker docker and have docker-xxx for whatever other brands they want to introduce? Reminds me of CoreOS rebranding as Container Linux.

Re: A new upstream project to break up Docker into independent components

#98
post #75

Hi all, Docker founder here. It appears that the explanation in the pull request is not very clear. Sorry about that. We didn't expect the PR to be the first thing people read: there is a new website at mobyproject.org. Unfortunately Github is struggling under the load, and I can't update the PR text to clarify. Here is an updated version with some clarifications: Docker is transitioning all of its open source collab…

If moby is not a replacement for docker (your words), why does docker/docker redirect to moby/moby (your actions)?

We moved the repository because the first task of the Moby project is to break up the Docker engine monolith into smaller components, and spin them out into separate repos. We started doing that with libnetwork, containerd, distribution etc, but we are not done yet. docker/docker is where that monolith lives, and where its maintainers work.

Once the componentization is complete, Moby will be an integration repository, with the tools necessary to combine upstream components into a complete system. We will use it to assemble Docker, and other system builders can use it to assemble alternatives to Docker.

Re: A new upstream project to break up Docker into independent components

#99
post #23

This is the one of the worst kind of business decision one can make. But I am not theirCTO and CEO. While not the same as Vagrant being replaced (and then revived because the alternate project was a burden), feels the same shitty decision IMO. Plently of people run successful OSS under the same name. Disappointing.

On the contrary. If you understand enterprise FOSS, then you understand that one of the primary benefits of FOSS for the enterprise contributing customer is the ability to to make the software more relevant for the enterprise through the enterprise's contributions to the FOSS project, at a rate which is typically unfeasible, if even possible, for closed commercial products.

By splitting up the open-source Docker CE codebase into smaller projects, each smaller project is more approachable to outside potential contributors. If Docker can succeed in increasing the number of contributors to the Moby projects, compared to the Docker CE project, then they'll have succeeded in increasing the relevance of their product in their target market, which translates to more customers, sales, and profits in the long-term.

Of course they run the business risk of a fork taking off, but in the real world, forks are arms races. They're easily won against dead or severely mismanaged projects, but against a project with a well-funded corporate sponsor? Few, if any, will have the resources to put into making a better fork than the original.

And like they said, for the vast majority of their customers, nothing is changing. Their customers bought a Docker product yesterday, and they're buying a Docker product tomorrow. That branding isn't changing.

Re: A new upstream project to break up Docker into independent components

#100
post #75

Hi all, Docker founder here. It appears that the explanation in the pull request is not very clear. Sorry about that. We didn't expect the PR to be the first thing people read: there is a new website at mobyproject.org. Unfortunately Github is struggling under the load, and I can't update the PR text to clarify. Here is an updated version with some clarifications: Docker is transitioning all of its open source collab…

So moby now uses containerd, which I guess is not related to systemd even though systemd also has its own container system. Are there any components to moby that are OSS and a part of the linux stack or is this whole endeavor to break away from linux dependencies?
Post reply on HN