\nIt is recomended when creating docker images that minimal images be used. In the case of Fedora it is recomended that for smallest images the minimal image should be used and “microdnf” be used instead of the full blown “dnf” package manager.\n<\/p>\n
\nOne major issue I have hit with using microdnf is that if a package in the main Fedora repositories is downgraded to a version below that shipped with the minimal image “microdnf” cannot handle downgrading packages when required.\n<\/p>\n
\nRe-doing a build that had been working for over four months it suddenly started failing with a conflict. The error I hit is below.\n<\/p>\n
\r\n.....\r\nUpgrading:\r\n glibc-2.29-22.fc30.x86_64 updates 4.2\\xc2\\xa0MB\r\n glibc-common-2.29-22.fc30.x86_64 updates 858.5\\xc2\\xa0kB\r\n glibc-minimal-langpack-2.29-22.fc30.x86_64 updates 48.4\\xc2\\xa0kB\r\n libxcrypt-4.4.10-1.fc30.x86_64 updates 125.3\\xc2\\xa0kB\r\nDowngrading:\r\n libstdc++-9.0.1-0.10.fc30.x86_64 fedora 583.9\\xc2\\xa0kB\r\nTransaction Summary:\r\n Installing: 204 packages\r\n Reinstalling: 0 packages\r\n Upgrading: 4 packages\r\n Removing: 0 packages\r\n Downgrading: 1 packages\r\nDownloading packages...\r\nRunning transaction test...\r\nerror: Error running transaction: package libstdc++-9.1.1-1.fc30.x86_64 (which is newer than libstdc++-9.0.1-0.10.fc30.x86_64) is already installed\r\n<\/pre>\n\nThe “microdnf” tool does not support usefull options “dnf” supports for resolving conflicts, in the case of conflicts like this the only solution is to switch to using the full “dnf” package. It requires changing the Dockerfile from…\n<\/p>\n
\r\nFROM registry.fedoraproject.org\/fedora-minimal:30\r\n...lots of stuff...\r\nRUN microdnf -y install perl procps-ng vim-minimal && microdnf clean all\r\n<\/pre>\n\nto the below…\n<\/p>\n
\r\nFROM registry.fedoraproject.org\/fedora-minimal:30\r\n...lots of stuff...\r\nRUN microdnf -y install dnf\r\nRUN dnf -y --allowerasing --obsoletes install perl procps-ng vim-minimal && dnf clean all && microdnf clean all\r\n<\/pre>\n\nThis results in a image size around 42Mb larger than just using microdnf, but it is unfortunately the only way to handle the issue.<\/p>\n","protected":false},"excerpt":{"rendered":"
It is recomended when creating docker images that minimal images be used. In the case of Fedora it is recomended that for smallest images the minimal image should be used and “microdnf” be used instead of the full blown “dnf” … Continue reading