From c630f3ba480a3c47dc8e4494678e7163f98ce116 Mon Sep 17 00:00:00 2001 From: Helin Wang Date: Tue, 28 Mar 2017 15:34:10 -0700 Subject: [PATCH] swap image and container order in doc --- .../build_and_install/docker_install_en.rst | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/doc/getstarted/build_and_install/docker_install_en.rst b/doc/getstarted/build_and_install/docker_install_en.rst index ddf3fbeaece..b4eced2d3d8 100644 --- a/doc/getstarted/build_and_install/docker_install_en.rst +++ b/doc/getstarted/build_and_install/docker_install_en.rst @@ -13,17 +13,6 @@ Working With Docker Docker is simple as long as we understand a few basic concepts: -- *container*: considering a Docker image a program, a container is a - "process" that runs the image. Indeed, a container is exactly an - operating system process, but with a virtualized filesystem, network - port space, and other virtualized environment. We can type - - .. code-block:: bash - - docker run paddlepaddle/paddle:0.10.0rc2 - - to start a container to run a Docker image, paddlepaddle/paddle in this example. - - *image*: A Docker image is a pack of software. It could contain one or more programs and all their dependencies. For example, the PaddlePaddle's Docker image includes pre-built PaddlePaddle and Python and many Python packages. We can run a Docker image directly, other than installing all these software. We can type .. code-block:: bash @@ -39,6 +28,17 @@ Docker is simple as long as we understand a few basic concepts: to download a Docker image, paddlepaddle/paddle in this example, from Dockerhub.com. +- *container*: considering a Docker image a program, a container is a + "process" that runs the image. Indeed, a container is exactly an + operating system process, but with a virtualized filesystem, network + port space, and other virtualized environment. We can type + + .. code-block:: bash + + docker run paddlepaddle/paddle:0.10.0rc2 + + to start a container to run a Docker image, paddlepaddle/paddle in this example. + - By default docker container have an isolated file system namespace, we can not see the files in the host file system. By using *volume*, mounted files in host will be visible inside docker container. -- GitLab