Fix inconsistencies in imagesandcontainers topic (#3801)

This commit is contained in:
Misty Stanley-Jones 2017-07-03 16:23:51 -07:00 committed by Victoria Bialas
parent 47108f2a49
commit 69c619e4c3
1 changed files with 3 additions and 3 deletions

View File

@ -23,14 +23,14 @@ instruction in the image's Dockerfile. Each layer except the very last one is
read-only. Consider the following Dockerfile: read-only. Consider the following Dockerfile:
```conf ```conf
FROM ubuntu:15.10 FROM ubuntu:15.04
COPY . /app COPY . /app
RUN make /app RUN make /app
CMD python /app/app.py CMD python /app/app.py
``` ```
This Dockerfile contains four commands, each of which creates a layer. The This Dockerfile contains four commands, each of which creates a layer. The
`FROM` statement starts out by creating a layer from the `ubuntu:15.10` image. `FROM` statement starts out by creating a layer from the `ubuntu:15.04` image.
The `COPY` command adds some files from your Docker client's current directory. The `COPY` command adds some files from your Docker client's current directory.
The `RUN` command builds your application using the `make` command. Finally, The `RUN` command builds your application using the `make` command. Finally,
the last layer specifies what command to run within the container. the last layer specifies what command to run within the container.
@ -74,7 +74,7 @@ differently, but all drivers use stackable image layers and the copy-on-write
## Container size on disk ## Container size on disk
To view the approximate size of a running container, you can use the `docker ps` To view the approximate size of a running container, you can use the `docker ps -s`
command. Two different columns relate to size. command. Two different columns relate to size.
- `size`: the amount of data (on disk) that is used for the writable layer of - `size`: the amount of data (on disk) that is used for the writable layer of