Description of problem:
Troy raised interesting points through mail, that we should take closer look:
Adam and I are on the Fedora Minimization team. One of the things
we are doing is looking at a few key containers to figure out how/if
we can get them smaller.
I've been going through the mariadb container and found two main ways
we could make it smaller.
1 - remove systemd from the container.
It has already been approved  that packages no longer *have* to
require systemd just because they have .service files. It has already
been removed as a dependency of dnf, and because of that, the F31 and
Rawhide images are already over 60M smaller.
mariadb-server depends on systemd, and thus, it's pulling that 60M
back in. I've looked, and I believe systemd can safely be removed as
2 - remove perl
This is a little more complicated. It depends on your vision for the
I saw that you moved all of your server perl scripts to
mariadb-server-utils. That is great. But the problem is that mariadb
has a couple of perl scripts as well, and mariadb-server depends on
If you feel that mariadb-server-utils are an important part of the
container, then we can just let things be.
If not, then the next question is, whether you feel mariadb (the
client tools) are an important part of the container. If you feel
they are, then we ask the question whether the two perl scripts in it
can be put into a -utils sub-package.
There is also the mariadb-server-backup, thats fairly big as well.
But again, it depends on what your vision of the mariadb container is.
What are your thoughts and ideas.
 - https://docs.fedoraproject.org/en-US/minimization/
 - https://pagure.io/packaging-committee/pull-request/890
 - https://minimization.github.io/reports/report-base-releases--fedora-container-base.html
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 32 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.