Skip to content

Commit

Permalink
fedora-container-toolbox: drop systemd
Browse files Browse the repository at this point in the history
Since change 48e2c3b this kickstart
is pulling in systemd.

This was noticed because since
b5fc5fd 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] containers/toolbox#1410

https://pagure.io/fedora-kickstarts/pull-request/1027
  • Loading branch information
ianw authored and debarshiray committed Mar 6, 2024
1 parent 465debb commit 531de62
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion fedora-container-toolbox.ks
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 531de62

Please sign in to comment.