DNS resolution does not work for built services in docker-compose. about for-win HOT 9 CLOSED

@derekssmith We have several compose tests which are run regular and most of them use the service name and they all pass. However, I don't think we have one where we pass the service name as part of the environment.

@friism could you take a look and maybe work with @derekssmith on an simpler repro?

from for-win.

To provide some more information on this. If I manually configure a network, and then provide "extra_hosts" to map the names to the IP addresses. It works.

I added this network configuration:

networks:
    internal:
        driver: bridge
        driver_opts:
            com.docker.network.enable_ipv6: "false"
        ipam:
            driver: default
            config:
                - subnet: 10.1.1.0/24
                  gateway: 10.1.1.1

I gave each of my services a manual ipv4_address. Then uses extra_hosts like this:

extra_hosts:
            - "zoo1:10.1.1.10"

NOTE: I only have to do this on the services that are built by docker-compose. The image services work as expected.

from for-win.

@derekssmith can you post output of docker version and docker-compose version please?

As Rolf mentioned, it be great if you could help narrow down the problem with a simpler repro or alternatively provide a repro that I can run with public images and/or a public project.

from for-win.

Here are the versions:

docker version

Client:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:15:28 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:15:28 2016
 OS/Arch:      linux/amd64

docker-compose version

docker-compose version 1.8.0, build d988a55
docker-py version: 1.9.0
CPython version: 2.7.11
OpenSSL version: OpenSSL 1.0.2d 9 Jul 2015

I will see if I can put a simple script together that will recreate the issue.

from for-win.

could you retry with Beta27 which we released today. with recent Beta's there have been a lot of improvements around DNS resolutions.
thanks

from for-win.

I installed Beta27 however I was not able to confirm the fix. Running docker-compose up sent the build process into an infinite loop, where it kept re-building two of my docker images over and over again.

from for-win.

I just tried again with the 1.12.3 release and it appears to be working. So whatever issue I was having before has been fixed in the latest stable release.

from for-win.

Thanks for getting back. The update had both compose and core engine updates, so maybe one of them did the trick. Glad that it's working for you and I'm closing the issue

from for-win.

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

from for-win.