-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Container urls not resolving #92
Comments
Hi ! From what I see from your log you have set the address of the container you've spawned as a nameserver, however you've launch dnsdock on your host so you shall add 127.0.0.1 in your resolver file instead |
Hi Thnx for the quick response! I have changed the nameserver to 127.0.0.1 and now i received the expected response, some debug output was dumped to! I will try further, the url isn't working yet but i guess their is something wrong in the container itself. Edit: still no succes, when i try to browse the urls i receive "ERR_NAME_NOT_RESOLVED" Thnx in advance! Kind regards |
I see that you are using a mac. Are you using docker toolbox or docker on mac ? Another user had a network issue on mac because he was using docker on mac. |
Jeps i am working on a mac :) this is the response from the ping request: |
And when you execute dig with the address 127.0.0.1 are you receiving something? |
` ; <<>> DiG 9.8.3-P1 <<>> 127.0.0.1 ;; QUESTION SECTION: ;; AUTHORITY SECTION: ;; Query time: 27 msec
I will check issue 89 :) |
`ERROR: for api Cannot start service api: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused "exec: \"/app/docker/apache/run.sh\": stat /app/docker/apache/run.sh: no such file or directory"\n" ERROR: for dnsdock Cannot start service dnsdock: driver failed programming external connectivity on endpoint test_dnsdock_1 (9886cba2805d1e91fb20c31e6ea152d8609e33ee5b2d978aa2649b7e6543901e): Error starting userland proxy: Bind for 172.20.200.1:53: unexpected error (Failure EADDRNOTAVAIL) I have tried the solution given in #89 .. the only difference is that i'm using the native docker. |
Docker for Mac has some issues on the netwoking aspect. This bug is not related to dnsdock |
Oooh oke, i will try that later today .. thnx for the quick response! |
@evancauwenberg @aacebedo |
@whitecolor .. tried it via docker-compose or just the native binary ./dnsdock |
@evancauwenberg show your docker-compose config for launching service? With docker for mac/windows you need to map docker.sock: |
Closing the issue as no activity has been registered since one month |
Hi!
First of all thnx for creating this little application!
I have followed the steps to build and run the dnsdock from source, when i start the application it seems to work:
[evancauwenberg@MacBook-Pro-van-Evert ~/go/bin]$ ★ sudo ./dnsdock -v 14:19:31.129 | DEBUG ▶ Handling DNS requests for 'docker'. 14:19:56.019 | DEBUG ▶ Started container 'b34830d018bd6228449dc3b4d7bb5d3945e1ea233b1f9c764da3283097357111' 14:19:56.030 | DEBUG ▶ Added service: 'b34830d018bd6228449dc3b4d7bb5d3945e1ea233b1f9c764da3283097357111': {api test [172.17.0.2] %!s(int=-1) [test.docker]}. 14:19:56.031 | DEBUG ▶ Handling DNS requests for 'test.docker'.
I have added also the following file in the /etc/resolver/
docker
nameserver 172.17.0.2
But when i use dig *.docker i don't receive the expected output:
`[evancauwenberg@MacBook-Pro-van-Evert ~]$
★ dig *.docker
; <<>> DiG 9.8.3-P1 <<>> *.docker
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1140
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;*.docker. IN A
;; AUTHORITY SECTION:
. 86392 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2017010700 1800 900 604800 86400
;; Query time: 22 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sat Jan 7 14:23:36 2017
;; MSG SIZE rcvd: 101`
Thnx in advance!
The text was updated successfully, but these errors were encountered: