4 ms·
Hey Solomon, here are some 'starters for 10': - Who will be able to use the Docker trademark? If someone built a fork of Docker CE from Moby, can they still ca
by crb 9y ago
Hey Solomon, here are some 'starters for 10':
- Who will be able to use the Docker trademark? If someone built a fork of Docker CE from Moby, can they still call it Docker? What about distribution packagers?
- Right now a single binary ('docker') is used to build images and runs clusters (among other things). As the monolith is broken down, will the new binaries still be named/branded 'docker'? Will there be rules about packaging only some of them? Will Docker CE/EE still have a single binary for all purposes?
- shykes 9y ago> Who will be able to use the Docker trademark? Docker. > If someone built a fork of Docker CE from Moby, can they still call it Docker? No. > What about distribution packagers? We're still working this out, with the guidance of a few distro packagers. There will most likely be a change of some sort, but don't want to rush anything until we are certain that it won't break users. > Right now a single binary ('docker') is used to build images and runs clusters (among other things). As the monolith is broken down, will the new binaries still be named/branded 'docker'? Yes. The same 'docker' binary will continue to exist. We are going to spin it out into its own repository under the docker github org. It will only act as a client, and we will encourage the development of a healthy ecosystem of alternative clients. > Will there be rules about packaging only some of them? Basically only Docker can create something called "Docker". Everything else will be regular open-source project rules: build, patch, package any way you want. > Will Docker CE/EE still have a single binary for all purposes? It depends on the target platform. Docker for Linux is a deb or rpm package with several binaries. Docker for AWS is a Cloudformation template. Docker for Mac is a Mac application with a very complex array of components built in. etc.