Docker 1.13 DNS A-Record Lookup works with services but not with stack deploy

i have a problem with docker stack deploy with an application that makes DNS-A-Record lookup for cadvisor-instances running on the different docker hosts.

while it worked just fine when starting the services separately

  • jenkins pipeline after run unit test karma script do not stop
  • How to place secure file in rancher storage?
  • Jenkins running in Docker on AWS EC2 can't retrieve http URLs, only https
  • docker-compose django-postgres error
  • How to saving a Docker container State?
  • docker phpmyadmin cant access localhost
  • cadvisor

    docker service create --network=custom_monitoring \
       --mode global --name cadvisor \
       --mount type=bind,source=/,target=/rootfs,readonly=true \
       --mount type=bind,source=/var/run,target=/var/run,readonly=false \
       --mount type=bind,source=/sys,target=/sys,readonly=true \
       --mount type=bind,source=/var/lib/docker/,target=/var/lib/docker,readonly=true google/cadvisor:latest
    

    my application (is public on docker-hub)

    docker service create --network=custom_monitoring \ 
       --publish 8080:8080 -e JAVA_OPTS="-Xmx256m -Dtarget.dnsname=tasks.cadvisor" \
       --name filter-proxy cproinger/sanalytics-filter-proxy
    

    deploying the services with the yml-file below and this docker command however

    docker stack deploy --compose-file myfile.yml mystack
    

    does not work (one can test with http://:8080/metrics, the response is not important just the log-output from the filter-proxy is which states if it could look up something with the dns-name). the sanalytics-filter-proxy does not get any DNS-Entries when querying for the cadvisor service (i also tried the dns names cadvisor, mystack_cadvisor, tasks.mystack_cadvisor and another service that does not use global mode (because i have another issue with that Docker 1.13 stack deploy with global service malfunction (target replicas increase without limit)) but since the lookup does not work for other services that do not have such an issue the DNS lookup has an issue of its own).

    version: "3"
    services:
    
    
    # monitoring services
      cadvisor:
        image: google/cadvisor:latest
        deploy: 
          mode: global  
        volumes:
          - /:/rootfs:ro
          - /var/run:/var:ro
          - /sys/sys:ro
          - /var/lib/docker:/var/lib/docker:ro
        networks:
          - app_overlay 
    
      filter-proxy:
        image: cproinger/sanalytics-filter-proxy
        ports: 
          - "8080:8080"  
        networks:
          - app_overlay
        depends_on: 
          - cadvisor
          - cep
        environment: 
          - JAVA_OPTS=-Xmx256m -Dsanalytics.slice.label=com.docker.stack.namespace -Dtarget.dnsname=tasks.cadvisor
    
    networks:
      app_overlay: 
    

    any suggestions why this does not work? am i just using the wrong dns-name or should i file a bug?

    i use docker 1.13 with experimental features switched on

  • Elastic Beanstalk deployment of Docker failing and reverting to old application version
  • Error pulling image (latest) from centos, Authentication is required
  • Kubernetes - Routable IP to individual Pods
  • Docker Python set utf-8 locale
  • How to get Docker work properly from within the msys2 bash?
  • How to retrain image on Windows
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.