docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Link to info about privileged containers (#5221)

This commit is contained in:
Misty Stanley-Jones 2017-11-06 14:31:21 -08:00 committed by GitHub
parent f9fcaac442
commit cfd10052b9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
engine/userguide/eng-image/dockerfile_best-practices.md
View File

@ -244,14 +244,14 @@ Probably the most common use-case for `RUN` is an application of `apt-get`. The
out for.
You should avoid `RUN apt-get upgrade` or `dist-upgrade`, as many of the
“essential” packages from the parent images won't upgrade inside an unprivileged
container. If a package contained in the parent image is out-of-date, you should
contact its maintainers.
If you know there’s a particular package, `foo`, that needs to be updated, use
“essential” packages from the parent images won't upgrade inside an
[unprivileged container](https://docs.docker.com/engine/reference/run/#security-configuration).
If a package contained in the parent image is out-of-date, you should contact its
maintainers. If you know there’s a particular package, `foo`, that needs to be updated, use
`apt-get install -y foo` to update automatically.
Always combine `RUN apt-get update` with `apt-get install` in the same `RUN`
statement, for example:
Always combine `RUN apt-get update` with `apt-get install` in the same `RUN`
statement. For example:
RUN apt-get update && apt-get install -y \
package-bar \