Summary: | systemd-nspawn doesn't updates /etc/resolv.conf | ||
---|---|---|---|
Product: | systemd | Reporter: | Maksim Melnikau <maxposedon> |
Component: | general | Assignee: | systemd-bugs |
Status: | RESOLVED FIXED | QA Contact: | systemd-bugs |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Maksim Melnikau
2012-11-17 21:48:23 UTC
This should be fixed in v184. Can you confirm that it works for you? (In reply to comment #1) > This should be fixed in v184. Can you confirm that it works for you? It still exists in systemd 195, I'm running systemd 195 on host and guest # systemctl --version systemd 195 systemd-nspawn -D /media/gsoho -b # stat /etc/resolv.conf stat: cannot stat ‘/etc/resolv.conf’: No such file or directory for the bind mount to work we currently need a stub file in the container, that we can overmount. We could first create an empty stub file i guess, but not sure that would be a good idea... Fixed in git. |
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.