From f23b12e4783140327261a8184b0bfdcef03b2da0 Mon Sep 17 00:00:00 2001 From: Daniel Preussker Date: Fri, 4 Dec 2020 18:31:51 +0100 Subject: [PATCH] Update systemd-9999.ebuild --- .../sys-apps/systemd/systemd-9999.ebuild | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/sdk_container/src/third_party/coreos-overlay/sys-apps/systemd/systemd-9999.ebuild b/sdk_container/src/third_party/coreos-overlay/sys-apps/systemd/systemd-9999.ebuild index a7ad60dc8c..35b304043f 100644 --- a/sdk_container/src/third_party/coreos-overlay/sys-apps/systemd/systemd-9999.ebuild +++ b/sdk_container/src/third_party/coreos-overlay/sys-apps/systemd/systemd-9999.ebuild @@ -196,16 +196,6 @@ src_prepare() { # Flatcar: We carry our own patches, we don't use the ones # from Gentoo. Thus we dropped the `if ! use vanilla` code # here. - # - # Flatcar: Use the resolv.conf managed by systemd-resolved. - # This shouldn't be necessary anymore. Added because of a bug - # https://github.com/systemd/systemd/issues/3826, which is - # apparently resolved in - # https://github.com/systemd/systemd/pull/5276 but another reason is - # that when /etc/resolve.conf is bind-mounted to a new network - # namespace it shouldn't contain the loopback IP address of the host - # which is not reachable from another network namespace. - sed -i -e 's,/run/systemd/resolve/stub-resolv.conf,/run/systemd/resolve/resolv.conf,' tmpfiles.d/etc.conf.m4 || die default }