Closed travier closed 1 year ago
Should we put it into the container file itself since it is essential to the image (not just extra)?
This file is used during the container build to include the package in the container.
This file is used during the container build to include the package in the container.
What I mean is - add it directly to the Containerfile
- same install command but explicitly on the command line there.
Because packages listed in extra-packages
are supposed to be 'extra' as the name suggests (i.e. optional) and one can expect to clean this file and the image to still be functional (which it won't be, without capsh
).
We don't split between "mandatory" and "extra" packages as far as I know.
Feel free to make a PR to create that split :)
We don't split between "mandatory" and "extra" packages as far as I know.
I consider whatever we install in the Containerfile
to be required for the image to function, by this logic - there is a split already :) For example, ubuntu-minimal
, ubuntu-standard
and libnss-myhostname
installed there are mandatory.
Opened #75 which reverts this partially (not the sort).
For example,
ubuntu-minimal
,ubuntu-standard
andlibnss-myhostname
installed there are mandatory.
The Git history says that /usr/local/sbin/unminimize
, ubuntu-minimal
and ubuntu-standard
were removed from ubuntu-toolbox:18.04
in commit 5cbaecde2f30ea1d to fix the build.
For example,
ubuntu-minimal
,ubuntu-standard
andlibnss-myhostname
installed there are mandatory.The Git history says that
/usr/local/sbin/unminimize
,ubuntu-minimal
andubuntu-standard
were removed fromubuntu-toolbox:18.04
in commit 5cbaecde2f30ea1d to fix the build.
I'm curious what happened there.. but it has worked before that and it works now (unminimizing and installing ubuntu-minimal and ubuntu-standard metapackages; plus other container are just like this). Hopefully it was just an intermittent failure...
Fixes: https://github.com/toolbx-images/images/issues/73