NetworkManager/tools/nm-guest-data/etc-rc.local.in

#!/bin/bash -e

/usr/bin/_nm-in-container-setup.sh

cat <<EOF > /etc/resolv.conf
# Generated by /etc/rc.d/rc.local
nameserver 8.8.8.8
EOF
contrib: setup "nm-in-container.sh" on start via rc.local script We need to mount sysfs, so that `ip netns exec` works. Do that automatically when starting the system container, via rc.local. While at it, use `podman build --squash-all` to speedup the building of the container image. 2022-09-09 16:07:01 +02:00			`#!/bin/bash -e`

			`/usr/bin/_nm-in-container-setup.sh`
nm-in-container: disable handling of "/etc/resolv.conf" in container and use 8.8.8.8. By default, podman bind mounts a "/etc/resolv.conf" file. That prevents NetworkManager (inside the container) to update the file, which leads to warnings in the log and certain NM-ci tests won't pass due to that. Disable handling of "/etc/resolv.conf" in podman. But also pre-deploy a default resolv.conf, with the google name server 8.8.8.8. I don't understand why, but even with "--dns=none", writing "/etc/resolv.conf" while building the container doesn't take effect. Instead, write a usable "/etc/resolv.conf" from "/etc/rc.d/rc.local". 2023-03-15 13:52:45 +01:00
			`cat <<EOF > /etc/resolv.conf`
			`# Generated by /etc/rc.d/rc.local`
			`nameserver 8.8.8.8`
			`EOF`