From 531de62a15a5ca1524478dd2098ffcc41d1106a1 Mon Sep 17 00:00:00 2001 From: Ian Wienand Date: Mon, 4 Dec 2023 12:09:10 +1100 Subject: [PATCH] fedora-container-toolbox: drop systemd Since change 48e2c3b5598de32f6dabfb5d1985d17aeab97d58 this kickstart is pulling in systemd. This was noticed because since b5fc5fd17d204870eebaa3f48f73e9f3c6d00697 started bringing in weak-dependencies, we started installing systemd-resolved is which created a symlinked /etc/resolv.conf in the image. Toolbox will not currently reset this on container start, as it is a symlink (this behaviour is a bit complicated; see [1]). This leads to an incompatability running the toolbox on *non* systemd-resolved hosts (e.g. RHEL9); you are left with a dangling symlink and no name-resolution in the toolbox. We do not want systemd in the toolbox image by default it; remove it from the list. Exclude systemd-resolved specifically, so if something else brings in systemd we still don't include this. [1] https://github.com/containers/toolbox/issues/1410 https://pagure.io/fedora-kickstarts/pull-request/1027 --- fedora-container-toolbox.ks | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/fedora-container-toolbox.ks b/fedora-container-toolbox.ks index a0254f0..3241f68 100644 --- a/fedora-container-toolbox.ks +++ b/fedora-container-toolbox.ks @@ -82,7 +82,10 @@ shadow-utils -shared-mime-info -sssd-client sudo -systemd +# This is a weak dependency of systemd, we do not want +# this in the container; see +# https://github.com/containers/toolbox/issues/1410 +-systemd-resolved tar # https://bugzilla.redhat.com/show_bug.cgi?id=1409920 tcpdump time