mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-05-01 14:58:05 +02:00
a6802cfa74
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".
8 lines
138 B
Bash
Executable file
8 lines
138 B
Bash
Executable file
#!/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
|