Merge pull request #5230 from huslage/master

Replacing ASCII art image with real diagram
Upstream-commit: 57cbe8b1060e28a365722341c52b1a8b69d368ba
Component: engine
This commit is contained in:
Sven Dowideit
2014-04-17 12:47:48 +10:00
2 changed files with 10 additions and 21 deletions
File diff suppressed because one or more lines are too long

After

Width:  |  Height:  |  Size: 8.2 KiB

@@ -28,28 +28,14 @@ efficiently: from development to production.
Let's take a look.
- Docker is a client-server application.
- Both the Docker client and the daemon *can* run on the same system, or;
- You can connect a Docker client with a remote Docker daemon.
- They communicate via sockets or through a RESTful API.
- Users interact with the client to command the daemon, e.g. to create, run, and stop containers.
- The daemon, receiving those commands, does the job, e.g. run a container, stop a container.
-- Docker is a client-server application.
-- Both the Docker client and the daemon *can* run on the same system, or;
-- You can connect a Docker client with a remote Docker daemon.
-- They communicate via sockets or through a RESTful API.
-- Users interact with the client to command the daemon, e.g. to create, run, and stop containers.
-- The daemon, receiving those commands, does the job, e.g. run a container, stop a container.
_________________
| Host(s) |
The Client Sends Commands |_________________|
------------------------- | |
[docker] <= pull, run => | [docker daemon] |
client | |
| - container 1 |
| - container 2 |
| - .. |
|_______~~________|
||
[The Docker Image Index]
P.S. Do not be put off with this scary looking representation. It's just our ASCII drawing skills. ;-)
![Docker Architecture Diagram](/article-img/architecture.svg)
## The components of Docker