Description of problem: The new paradigm of computing involves creating a lot of light weight containers. However, the minimal install for mageia runs at about 200 MB, whereas a container for Alpine Linux runs at about 20 MB. The relatively large size of a minimal Mageia container has to do with 1) the current packaging contains a large number of requires from basesystem-minimal and initscripts. Containers do not use init scripts to start up leading to a lot of bloat Suggest converting a lot of "requires" in initscripts and basesystem-minimal to recommends. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. create image with cauldron 2. 3.
Thank you for the suggestion. This looks a wide-ranging issue, so assigning it globally; CC tmb for 'basesystem'.
CC: (none) => tmbAssignee: bugsquad => pkg-bugs
This has been discussed in the past in relation to providing virtualbox, docker and other types of container images. Providing tools to allow people to easily create their own container images is fine. While individuals are free to distribute Mageia based images, they must not be distributed as officially Mageia supported images. Otherwise every image must be rebuilt and retested every time any one of the packages contained in those images is updated. That would have an impact on the security and qa teams as the number and/or types of images increases, which we don't have the capacity to handle.
CC: (none) => davidwhodgins
We (or actually ngompa) will create a basesystem-containers subpackage that will try to address the deps needed for containers so we wont break basesystem-minimal As for converting requires to recommends, then for most cases that is a NO-GO as it will be way too easy for endusers to break their systems if they can remove a package that is only recommended. Of course the deps can be reviewed, but we will be very strict about what we will allow
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=28756