Bug 90336 - Systemd-nspawn doesn't updates /etc/resolv.conf
Summary: Systemd-nspawn doesn't updates /etc/resolv.conf
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-06 12:15 UTC by reji
Modified: 2018-07-18 14:25 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description reji 2015-05-06 12:15:10 UTC 
I have ext4 filesystem on /dev/sda9 mounted on / and btrfs on /dev/sda10 mounted on /var/lib/machines.

After pulling images via machinectl pull-tar and running container via systemd-nspawn -M machinename, i got an error:

"Failed to copy /etc/resolv.conf to /var/lib/machines/ubuntu/etc/resolv.conf: Too many levels of symbolic links"

I think this is cuz systemd-nspawn create hard link instead of copy /etc/resolv.conf in to container
Comment 1 Lennart Poettering 2018-07-18 14:25:12 UTC 
This should be fixed with current systemd-nspawn, in particular the new --resolv-conf= option there is in 239. Closing hence.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.