mirror of
https://github.com/mageddo/dns-proxy-server.git
synced 2026-04-25 17:35:54 +03:00
[GH-ISSUE #63] dns resolve during image build #27
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#27
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 @johnbritto1 on GitHub (Apr 3, 2018).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/63
dns-proxy-log.txt
Hi,
I am using docker eclipse tooling to connect with the remote docker instance using TLS.
The docker build RUN could not resolve dns for command "apt-get install package".
Here is the error shown by dns-proxy-server
[36m18-04-03 06:42:00.016 DEB [0mid=53, m=handleQuestion status=not-resolved, solver=proxy.DockerDnsSolver, err=hostname not found opqobwuqbukhds
[36m18-04-03 06:42:00.016 DEB [0mid=54, m=handleQuestion status=not-resolved, solver=proxy.DockerDnsSolver, err=hostname not found jqwjuxddshtl
Any workaround. If I stop the dns-proxy-server, docker build could resolve the DNS.
I have attached the complete log.
Thanks.
@mageddo commented on GitHub (Apr 28, 2018):
@johnbritto1 Sorry for the too late answer
apt-get updateworks great?opqobwuqbukhds sounds like a local hostname, I don't think it's related to apt-get. I saw the only one debian server question was successfully answered
You could try add a custom DNS server (you can get some taking a look at
/etc/resolv.conf) at config file/opt/dns-proxy-server/conf/config.json@johnbritto1 commented on GitHub (Apr 30, 2018):
Hello Mageddo,
Thanks for reply.
To answer you questions.
After adding the dns-server entry in /etc/docker/daemon.json file..
"dns": ["8.8.8.8", "8.8.4.4"],
the issue resolved.
Thanks,
John
@mageddo commented on GitHub (Apr 30, 2018):
Thanks for sharing the solution, it would be helpful in the future
@ilbertt commented on GitHub (Aug 18, 2022):
I'm also had this problem after setting up the dns-proxy-server.
@mageddo do you have any idea of what's causing it?