From f50041640647d53e1f5ceb010d9c0a7c087cfb33 Mon Sep 17 00:00:00 2001 From: Pradyun Gedam Date: Fri, 18 Mar 2022 17:41:59 +0000 Subject: [PATCH] PEP 668: Keep the marker file in container images (#2289) This preserves the protections afforded by these changes, in container images. --- pep-0668.rst | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/pep-0668.rst b/pep-0668.rst index db17095b0..32d5c53d1 100644 --- a/pep-0668.rst +++ b/pep-0668.rst @@ -659,18 +659,14 @@ on Debian) depends on pipx. .. _pipx: https://github.com/pypa/pipx -Remove the marker file in container images ------------------------------------------- +Keep the marker file in container images +---------------------------------------- Distros that produce official images for single-application containers -(e.g., Docker container images) should remove the +(e.g., Docker container images) should keep the ``EXTERNALLY-MANAGED`` file, preferably in a way that makes it not -come back if a user of that image installs package updates inside -their image (think ``RUN apt-get dist-upgrade``). On dpkg-based -systems, using ``dpkg-divert --local`` to persistently rename the file -would work. On other systems, there may need to be some configuration -flag available to a post-install script to re-remove the -``EXTERNALLY-MANAGED`` file. +go away if a user of that image installs package updates inside +their image (think ``RUN apt-get dist-upgrade``). Create separate distro and local directories --------------------------------------------