Bug 90336

Summary:	Systemd-nspawn doesn't updates /etc/resolv.conf
Product:	systemd	Reporter:	reji <i.s.reji>
Component:	general	Assignee:	systemd-bugs
Status:	RESOLVED FIXED	QA Contact:	systemd-bugs
Severity:	minor
Priority:	medium	CC:	i.s.reji
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

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.