DNS resolver broken inside systemd-container

[ant9000]

I've successfully used a debos recipe on my laptop, but the same recipe fails on my home workstation - debootstrap cannot proceed because the container does not resolve DNS names. My problem is maybe related to #101 and #48.

Both machines are Debian Stretch, and I can't find out any relevant difference between the two. Laptop is connected via wifi and workstation via ethernet - don't think it matters, though.

Putting the following action as the first one solves the problem:

  - action: run
    description: fix DNS inside container
    script: /bin/ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf 

This is acceptable as workaround, but I'd say DNS stuff should be entirely handled by debos and not by any recipe.

Antonio

[gustavosbarreto]

Any news on this issue? I'm facing the same issue

[jeremiah]

This workaround might be best as an addition to the recipe because having "resolv.conf" in /run/systemd/resolve/ is not a universal distro standard. On Debian based distros for example resolv.conf ends up in /lib/systemd/resolv.conf as opposed to /run/systemd/resolve/resolv.conf. I imagine it will be hard to predict where it will end up for each value of ${distro}.

[ant9000]

I am using plain Debian, both as host and for the generated image, and the workaround I've suggested does work there - so I guess it won't be a distro problem.

But even if my recipe snippet works, I'd suggest that adding explicit resolution configuration to systemd-nspawn, via its --resolv-conf parameter, would be a cleaner way of obtaining the same result.