diff --git a/docs/sources/article-img/architecture.svg b/docs/sources/article-img/architecture.svg new file mode 100644 index 0000000000..607cc3c18f --- /dev/null +++ b/docs/sources/article-img/architecture.svg @@ -0,0 +1,3 @@ + + +2014-04-15 00:37ZCanvas 1Layer 1HostContainer 1Container 2Container 3Container ...Docker Clientdocker pulldocker rundocker ...Docker IndexDocker Daemon diff --git a/docs/sources/introduction/technology.md b/docs/sources/introduction/technology.md index ba1e09f0d7..6ae7445595 100644 --- a/docs/sources/introduction/technology.md +++ b/docs/sources/introduction/technology.md @@ -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