Daniel P. Berrangé <berrange@redhat.com> writes:
> The container runtime in the host OS will have configured most mount
> points before the container starts. It would be relatively uncommon
> for processes inside the container image to need to mount additional
> volumes later.
That's fair, but util-linux contains many other tools that may be useful
at runtine within a containerized tool (logger, flock, lsmem, rename,
taskset, whereis, others?). Some those be moved somewhere else?
/usr/bin/* files from f33's util-linux:
cal chmem choom chrt col colcrt colrm column dmesg eject fallocate
fincore findmnt flock getopt hardlink hexdump i386 ionice ipcmk ipcrm
ipcs irqtop isosize kill last lastb linux32 linux64 logger login look
lsblk lscpu lsipc lsirq lslocks lslogins lsmem lsns mcookie mesg more
mount mountpoint namei nsenter prlimit raw rename renice rev script
scriptlive scriptreplay setarch setpriv setsid setterm su taskset ul
umount uname26 unshare utmpdump uuidgen uuidparse wall wdctl whereis
write x86_64
It is all about tradeoff between what **may** be useful and the size of the base image. In the container base image space, size is very important (see how successful is Alpine) and we have to make tradeoff in terms of what tools are included by default in the image.
To get an idea on how Fedora does compared to some other distros
- FChE
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure