Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
resolv.conf is emptied few seconds after boot with static networking #1140
Since our beta machines have been upgraded to 899.8.0, the DNS servers entries disappear from /etc/resolv.conf a few seconds after boot.
We are running with a static networking setup as described here.
Sample from cloudconfig:
write_files: - path: /etc/systemd/network/static.network permissions: "0644" content: | [Match] Name=en* [Network] Address=172.21.40.112/23 Gateway=172.21.41.254 DNS=188.8.131.52 DNS=184.108.40.206 coreos: units: - name: systemd-networkd.service command: start
Systemd-networkd stops a few seconds after boot because there are no DHCP leases (this 'feature' was introduced in v219, networkd stops when idle.) When restarting systemd-networkd.server the resolv.conf is correctly updated, but emptied again a few seconds later.
referenced this issue
Feb 26, 2016
we're working on getting alpha/beta out that reverts coreos/systemd#30, but in the meantime you can roll back via https://coreos.com/os/docs/latest/manual-rollbacks.html. you will probably want to disable either locksmithd or update-engine temporarily until the update goes out. i'll leave a note when alpha and beta are ready.
In case somebody else is running into massive issues b/c of this, here is a quick (tmp) fix:
Once Beta is fixed, the file has to be removed & the symlink restored. Thanks @mischief and wCPO for your help!