Bug 2020852
| Summary: | systemd: /etc/resolv.conf is initialized to systemd-resolved symlink even when it is not installed | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Petr Menšík <pemensik> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 35 | CC: | dtardon, fedoraproject, filbranden, flepied, lnykryn, msekleta, ryncsn, ssahani, s, systemd-maint, yuwatana, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-24 08:51:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1313085 | ||
| Bug Blocks: | |||
|
Description
Petr Menšík
2021-11-06 12:53:02 UTC
Created PR 21257 [1] on systemd upstream. Avoid creation of such link if user intention is unknown. Ensure it is always present when systemd-resolved.service enabled, but leave its status to any different service otherwise. It seems such solution is more appropriate. 1. https://github.com/systemd/systemd/pull/21257 Tried with podman fedora:rawhide container. Because it prepares /etc/resolv.conf as simple file, which even cannot be removed from the container. Podman works. But it does not allow on any systemd-init enabled container to have /etc/resolv.conf missing. If network is configured in a static way outside the container, I guess resolv.conf should be prepared by any such tooling. Be it cloud-init or anything similar. Even with missing /etc/resolv.conf, container can have working name resolution. It is only required to forward its ports 127.0.0.1:53 and [::1]:53 to the host, which might run common cache for all containers. I guess such configuration is not possible without tmpfiles.d/etc.conf override. |