From bce3cbf09d5057395de588b8d30872b97dd1cb20 Mon Sep 17 00:00:00 2001 From: Itamar Turner-Trauring Date: Thu, 25 Mar 2021 08:41:05 -0400 Subject: [PATCH] Stop telling people not to install security updates --- develop/develop-images/dockerfile_best-practices.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/develop/develop-images/dockerfile_best-practices.md b/develop/develop-images/dockerfile_best-practices.md index d017bbdd68f..dbc7d53457a 100644 --- a/develop/develop-images/dockerfile_best-practices.md +++ b/develop/develop-images/dockerfile_best-practices.md @@ -469,13 +469,6 @@ Probably the most common use-case for `RUN` is an application of `apt-get`. Because it installs packages, the `RUN apt-get` command has several gotchas to look out for. -Avoid `RUN apt-get upgrade` and `dist-upgrade`, as many of the "essential" -packages from the parent images cannot upgrade inside an -[unprivileged container](../../engine/reference/run.md#security-configuration). If a package -contained in the parent image is out-of-date, contact its maintainers. If you -know there is 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: