You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the bug is.
Steps To Reproduce
Steps to reproduce the behavior:
set up a NixOS host with all default network settings (DHCP)
declare a NixOS container with all default network settings (share host's container namespace and copy it's resolv.conf) and with container.<name>.autoStart = true
reboot the host
observe the /etc/resolv.conf in the container even after the host's DHCP request has successfully populated the host's resolv.conf. compare host and container resolv.conf:
[root@github-runner-host:~]# cat /etc/resolv.conf
# Generated by resolvconf
domain contaboserver.net
nameserver 161.97.189.51
nameserver 161.97.189.52
options edns0
[root@github-runner-host:~]# nixos-container run githubRunner0 cat /etc/resolv.conf
# Generated by resolvconf
options edns0
options edns0
reboot the container and see the resolv.conf updated
Describe the bug
A clear and concise description of what the bug is.
Steps To Reproduce
Steps to reproduce the behavior:
container.<name>.autoStart = true
Expected behavior
container has functional DNS resolving on first boot
Metadata
rev: 83b198a
Workaround
tell systemd.nspawn to bind-mount the hosts's resolv.conf:
The text was updated successfully, but these errors were encountered: