mirror of
https://github.com/mageddo/dns-proxy-server.git
synced 2026-04-25 09:25:56 +03:00
[GH-ISSUE #329] Automatically restart system-resolved when running inside a docker container #117
Labels
No labels
bug
confirmed
discussion
duplicate
enhancement
feature
feature-request
not-planned
pull-request
secondary-feature
stale
triage
waiting-feedback
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/dns-proxy-server-mageddo#117
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mageddo on GitHub (Feb 28, 2023).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/329
5 => DPS will try workarounds to automatically restart system-resolved when running inside a container
Below some references of possible workarounds, if DPS fails or the requirements of the workarounds were not available it will only log that won't possible to restart systemd-resolved and ask the user to do that as said in scope 1
@mageddo commented on GitHub (Mar 5, 2023):
I'm considering that maybe this feature doesn't makes sense, docker containers are made to isolate programs execution from their hosts, if the program is intended to make changes at the host them this program just should run at the host, without a docker container.
For now I will advise people to run DPS without docker or to run DPS on docker on host network mode or with a static IP then they will be able to manually configure the DNS server at the host at once.
@mageddo commented on GitHub (Mar 5, 2023):
Docs were updated