Hi, On Sun, Aug 20, 2017 at 05:40:20PM -0400, Theodore Ts'o wrote: [...] > The normal Debian Docker images uses --variant=minbase. So changing > e2fsprogs from Priority: required to Priority: important **will** > change the Docker image. Ref: > > https://github.com/moby/moby/blob/master/contrib/mkimage.sh
I thought tianon did the official images. Just goes to show how out of the loop I am with docker these days. I'd recommend they add a '--include=mount,fdisk,e2fsprogs' to their debootstrap command for the future (in their non-slim version(s)?) if they want to be sure to preserve the tools in their base image for the future. [...] > > I think you're entangling two different changes: > > 1) Essential: yes->no > 2) Priority: required->important > > No? Yes. Your 1) and 2) is what I initially called "step 1" and "step 2" to try to indicate they are to separate distincts steps. Step 1: Essential: yes -> Important: yes Step 2: Priority: required -> Priority: important > > We can make the first change without the second. The first allows us > packages to declare dependencies. The second shrinks the minbase > size. And that's why I was asking the question what problem exactly > that we being solved here. Since if it's just the dependency issue, > we can change Essential to No. I'm perfectly happy if we just do step 1 for buster (upcoming release). I think it would be nice to atleast keep the option open for discussion of doing also step 2 later (in Bullseye?, release after Buster -- about 4-5 years from now), if you think doing it for buster is too agressive. The main reason for doing 'step 2' would be to make 'minbase' a "slim" version of debian "out of the box" (without tweaks needed. Basically same motivation as for splitting out the locales of minbase packages.) Regards, Andreas Henriksson
