Hi,
I'm trying to understand for to create docker container images using
"guix pack". For this I created a simple container image by running
guix pack --format=docker httpd
The resulting image contains quite some package which IMHO are not
required by apache httpd:
apr apr-util bash-minimal bash-static binutils bzip2 coreutils expat
file gawk gcc glibc glibc grep guile httpd ld-wrapper libffi libgc
libltdl libstdc++ libunistring libxcrypt openssl pcre perl pkg-config
sed xz
as well as some generated packages: emacs-subdirs/ info-dir/ profile/
And indeed, "guix graph -t references --path httpd …" for all packages
contained in the image shows that httpd does not require many of the
packages included:
libstdc++: unknown package
no path _ to '…-gcc-toolchain-14.3.0'
no path _ to '…-glibc-toolchain-2.41
no path … to '…-bash-minimal-5.2.37'
no path … to '…-bash-static-5.2.37'
no path … to '…-binutils-2.44'
no path … to '…-bzip2-1.0.8'
no path … to '…-coreutils-9.1'
no path … to '…-file-5.46'
no path … to '…-gawk-5.3.0'
no path … to '…-glibc-2.41'
no path … to '…-grep-3.11'
no path … to '…-guile-3.0.9'
no path … to '…-libffi-3.4.6'
no path … to '…-libgc-8.2.8'
no path … to '…-libunistring-1.3'
no path … to '…-pkg-config-0.29.2'
no path … to '…-sed-4.9'
no path … to '…-xz-5.4.5'
What can we do to avoid adding such packages into an image?
PS: This bad behavior matches the pattern that installing a package from
substitutes also installs many build-tools like gcc or llvm.
--
Regards
Hartmut Goebel
| Hartmut Goebel |[email protected] |
|www.crazy-compilers.com | compilers which you thought are impossible |
