2

I have followed the instructions at http://doc-en.tuleap.net/en/latest/developer-guide/quick-start/run-tuleap.html, but hitting http://tuleap_web_1.tuleap-aio-dev.docker/ gives "Server not found". The first two points under "3.4. Troubleshooting" seem OK, but the third one gives ";; connection timed out; no servers could be reached" on both the dig '*.docker', dig '*.tuleap-aio-dev.docker' and dig 'tuleap_web_1.tuleap-aio-dev.docker' commands.

Unfortunately, there are no follow up tips for when these commands fail. I will add that if I can solve the problem.

Captnbli
  • 21

1 Answers1

0

It seems to be related to lack of dnsdock working properly. The easiest way to go would be to capture the IP the web container:

docker inspect -f '{{.NetworkSettings.IPAddress}}' tuleap_web_1

and to set the result in your /etc/hosts like:

172.17.0.4    tuleap_web_1.tuleap-aio-dev.docker

You will have to update the IP address each time you start the container.

Manuel VACELET
  • 349
  • 2
  • 7