[systemd-devel] /etc/resolv.conf link in container

Johannes Ernst johannes.ernst at gmail.com
Tue Jun 16 14:39:13 PDT 2015

I have a root filesystem in directory foo/
It has symlink
    foo/etc/resolv.conf -> /run/systemd/resolve/resolv.conf

When I’m booting the container:
    sudo systemd-nspawn --directory foo --boot

I’m getting:
    Failed to copy /etc/resolv.conf to /home/…./foo/etc/resolv.conf: Too many levels of symbolic links

This message makes very little sense to me. Why is a copy necessary? and is that indeed /etc/resolv.conf or foo/etc/resolv.conf?

If I boot with -n, I don’t seem to get the error.



More information about the systemd-devel mailing list