How to find other container in docker when using consul dns resolver

Questions
1

Kong version: v0.13

Now i have already configured Kong using consul dns resover

config file like that

dns_resolver = 192.168.8.6:8600
dns_order = A,SRV,CNAME

Then i found Kong can not work right,
the error log as below:

2018/08/29 18:22:16 [debug] 1#0: [lua] client.lua:545: init(): [dns-client] nameserver 192.168.8.6:8600


2018/08/29 18:22:16 [debug] 1#0: [lua] client.lua:550: init(): [dns-client] attempts = 5


2018/08/29 18:22:16 [debug] 1#0: [lua] client.lua:559: init(): [dns-client] timeout = 2000 ms


2018/08/29 18:22:16 [debug] 1#0: [lua] client.lua:563: init(): [dns-client] ndots = 0


2018/08/29 18:22:16 [debug] 1#0: [lua] client.lua:565: init(): [dns-client] search = 


2018/08/29 18:22:16 [debug] 1#0: [lua] client.lua:571: init(): [dns-client] badTtl = 30 s


2018/08/29 18:22:16 [debug] 1#0: [lua] client.lua:573: init(): [dns-client] emptyTtl = 1 s


2018/08/29 18:22:16 [debug] 1#0: [lua] client.lua:431: init(): [dns-client] (re)configuring dns client


2018/08/29 18:22:16 [debug] 1#0: [lua] client.lua:435: init(): [dns-client] staleTtl = 4


2018/08/29 18:22:16 [debug] 1#0: [lua] client.lua:438: init(): [dns-client] noSynchronisation = false


2018/08/29 18:22:16 [debug] 1#0: [lua] client.lua:457: init(): [dns-client] query order = A, SRV, CNAME


2018/08/29 18:22:16 [crit] 21#0: *3 [lua] balancer.lua:685: init(): failed loading initial list of upstreams: failed to get from node cache: [postgres error] [toip() name lookup failed]: dns server error: 2 server failure, context: ngx.timer

It looks likes Kong can not find postgres database by consul dns, is there anyway to find docker’s container which is in same network?

2

I have the same problem. Did you find a solution?

3

I did a docker-compose sample: https://github.com/flowdopip/kong-consul

but i have an error when kong call the upstream

{
“message”: “An unexpected error occurred”
}