Also talk about Docker, Moby and Rancher
Last week's DockerCon, Docker officially opened the Moby project – the Docker component into a series of assemblies. DockerCon has a simple demo, with moby tools to assemble the various components into a custom Linux operating system image. It looks cool, but it also makes a lot of people confused. At the same time, Moby's hot debate and controversy have never stopped.
The contents of the training include: Kubernetes overview, architecture, log and monitoring, deployment, automatic driving, service discovery, network solutions and other core mechanism analysis, advanced articles – Kimbernetes scheduling work principle , Resource management and source code analysis.
- How to use the API to initialize the Rancher server - for future automation
- Rancher v1.2 new version of the bright spot analysis
- Container: make "infrastructure code" easier
- New CEO took office, Docker made a choice between open source and business?
- DockOne WeChat sharing (16): a joint-stock commercial bank customization PaaS introduction
- Containers and applications: expansion, refactoring or rebuilding?
The author of this article is Rancher Labs's chief architect and co-founder Darren Shepherd, also Docker's maintainer. We would like to provide some background and explanation of the Moby project and how it will affect Rancher, RancherOS and our users.
Moby project some background
In fact, a few months ago, the Moby project on the discussion has been launched between the Docker Project maintainer, all this is because Docker is a product, but also a project of the dual nature. This duality in the beginning is to Docker (both refers to the Docker project, also refers to Docker company) has brought a lot of benefits. But in the end, Docker company must go to the decision of the intersection, to determine their products in the end what should be, what is the future direction. As a Docker maintainer we believe that products and projects should really be separated.
Docker's ultimate goal is to further integrate Docker on the basis of past work. Docker's componentization is not a fresh issue, and this work has been going on for a long time, starting with runc and containerd, which has long been the target of the Docker project. Thanks to a thousand contributors and maintainer, so far, Docker is still a well-organized library and package.
The Moby project transforms the Docker project into a fully modular architecture and provides new ownership for the vast majority of Docker code, not the product itself. Moby allows our community members to make more contributions to the innovation and development of container technology in an unprecedented way. Today, we can handle some very useful use cases from a technical point of view, but this is in conflict with previous Docker products. For example, RancherOS is such a use case.
How does Moby affect Rancher, RancherOS and our users?
So what does Moby do with Rancher, RancherOS and our users? The answer is that most users will not see any changes: Docker or Docker. It will continue to be your understanding and favorite Docker (and there may be a better internal architecture).
What will you see in RancherOS? RancherOS is a highly specialized container application that is the operating system for all components that are containers. To make RancherOS possible, we need some real low-level knobs in Docker. And even if this may be detrimental to Docker UX, Docker still offers us many of these knobs. For example, – uts = host: I guess 99% of Docker users do not know what this tag is, but RancherOS needs it, with it, DHCP can dynamically propagate the host name changes.
In the long run, the Moby project will give RancherOS a positive help. We can keep the same Docker user interface, but with Moby we can access all the low-level Linux knobs we need. Finally, the user will have a more lightweight, faster, and more secure RancherOS. The Moby project is also very good for Rancher: Rancher is designed to manage Docker containers, and in the future we can manage custom Linux components assembled from Moby Project.
Written at the end …
Moby triggered the heat is still not stop, the industry also has a lot of questions and dissatisfaction with the voice. And we just want to focus on the more positive side, and Docker users, Rancher users and container ecosystems together, continue to open source for the development of the container to contribute.
Source: Rancher Labs