mirror of
https://pagure.io/fedora-kickstarts.git
synced 2024-12-22 05:35:26 +00:00
fedora-container-toolbox: drop systemd
Since change48e2c3b559
this kickstart is pulling in systemd. This was noticed because sinceb5fc5fd17d
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
This commit is contained in:
parent
465debb7c9
commit
531de62a15
@ -82,7 +82,10 @@ shadow-utils
|
|||||||
-shared-mime-info
|
-shared-mime-info
|
||||||
-sssd-client
|
-sssd-client
|
||||||
sudo
|
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
|
tar # https://bugzilla.redhat.com/show_bug.cgi?id=1409920
|
||||||
tcpdump
|
tcpdump
|
||||||
time
|
time
|
||||||
|
Loading…
Reference in New Issue
Block a user