3 ms·

Both Machine and Swarm are not baked into Docker – they are separate projects and binaries: https://github.com/docker/machine https://github.com/docker/machine

by bfirsh 12y ago

Both Machine and Swarm are not baked into Docker – they are separate projects and binaries: https://github.com/docker/machine https://github.com/docker/machine https://github.com/docker/swarm https://github.com/docker/swarm Compose is still in the design proposal stage. We want to hear whether you think it should be built into Docker or not: https://github.com/docker/docker/issues/9459 https://github.com/docker/docker/issues/9459

23david 12y ago
Docker Machine looks to be a revision/rebrand of your docker hosts proposal made in the last 1-2 days or so. Very confusing. The proposal discussion: https://github.com/docker/docker/issues/8681 https://github.com/docker/docker/issues/8681 Rename "docker hosts" to "docker machines": https://github.com/bfirsh/docker/commit/e6abec4033f48d1cad31380f3c94da137b64ae74 https://github.com/bfirsh/docker/commit/e6abec4033f48d1cad31... 2 days ago, from you: I have now rebased the host management branch on top of #8265 and squashed it: https://github.com/bfirsh/docker/compare/host-management Any pull requests should now be based on top of that. The driver interface hasn't changed, so it should be a trivial matter to rebase any existing pull requests. The main thing which has changed is that drivers are expected to set up identity auth for communication with the host. See this commit for an example of how to do so. The old branch is here for reference. Full update and preview builds coming soon." 1 day ago, a message from tianon, core Docker maintainer: Has there been any progress on splitting the actual driver implementations out of the core binary? And now this. Color me confused.
- mynameisvlad 12y ago
  The proposal was made in October, no? The only thing that happened 2 days ago was renaming it to "docker machines". So unless I misread the thread, your timeline is a bit off.
deniszgonjanin 12y ago
As a heavy fig user, it seems compose is really just fig, but rewritten in Go and merged into Docker. It should be kept as a separate project, if modularity and a 'tight core' really is the long term plan for the future of Docker.

by bfirsh 12y ago

23david 12y ago

Docker Machine looks to be a revision/rebrand of your docker hosts proposal made in the last 1-2 days or so. Very confusing. The proposal discussion: https://github.com/docker/docker/issues/8681 https://github.com/docker/docker/issues/8681 Rename "docker hosts" to "docker machines": https://github.com/bfirsh/docker/commit/e6abec4033f48d1cad31380f3c94da137b64ae74 https://github.com/bfirsh/docker/commit/e6abec4033f48d1cad31... 2 days ago, from you: I have now rebased the host management branch on top of #8265 and squashed it: https://github.com/bfirsh/docker/compare/host-management Any pull requests should now be based on top of that. The driver interface hasn't changed, so it should be a trivial matter to rebase any existing pull requests. The main thing which has changed is that drivers are expected to set up identity auth for communication with the host. See this commit for an example of how to do so. The old branch is here for reference. Full update and preview builds coming soon." 1 day ago, a message from tianon, core Docker maintainer: Has there been any progress on splitting the actual driver implementations out of the core binary? And now this. Color me confused.

mynameisvlad 12y ago
The proposal was made in October, no? The only thing that happened 2 days ago was renaming it to "docker machines". So unless I misread the thread, your timeline is a bit off.

deniszgonjanin 12y ago

As a heavy fig user, it seems compose is really just fig, but rewritten in Go and merged into Docker. It should be kept as a separate project, if modularity and a 'tight core' really is the long term plan for the future of Docker.