Docker Weave and WeaveDNS issues

I’m having an issue with setting up weaveDNS on a small weave network that I have running on my local machine.

For now the problem manifests itself in the fact that when I run ‘weave status’ I’m not seeing a DNS section in the output (as its suggested in the Troubleshooting section of http://docs.weave.works/weave/latest_release/weavedns.html).

  • Using the Spotify Maven Docker plugin, how can I change the file permissions of a resource that I add to a Docker container?
  • Hashes in `docker pull wordpress`
  • Is there a formula for calculating the overhead of a Docker container?
  • dotnet aspnetcore docker build fails with a 145 error code
  • Detailed Docker Service Error Output
  • how to update docker in coreos
  • I’m running 4 containers. weave ps output is:

    c1d106ed5717 c2:ce:53:49:98:f6 10.0.1.12/24  
    8f01765b2ba6 ba:2e:c3:4b:8f:8f 10.0.1.30/24  
    0d824d914383 ae:95:28:db:95:18 10.0.1.11/24  
    6cf985b91e9a 12:82:31:c2:b4:49 10.0.1.10/24  
    b43f86e9fb51 d6:2e:d4:6a:09:dc **10.0.1.200/24**  
    2847dd89e90d be:8b:d5:74:07:94
    

    The highlighted container (10.0.1.200) is the weaveDNS container. The final container (2847dd89e90d) is the Weave router container.

    I’m starting containers with:

    sudo weave run --with-dns 10.0.1.30/24 -h service.weave.local --name service service_img_name 
    

    Does anyone have an idea why weave status is not showing a DNS section?
    If you need me to give you additional info on the Weave setup, please let me know.

  • Deleting all Docker images from a repository
  • How does docker manage to get a return code of 200 instead of 401
  • Flask-WTF CSRF validation fails when app moved to docker production environment
  • How can Docker run distros with different kernels?
  • Windows based couchbase image for docker
  • Not able to execute RUN commands in Dockerfile
  • One Solution collect form web for “Docker Weave and WeaveDNS issues”

    Are you using a release version (0.9.0 at time of writing) of weave?

    $ sudo weave version
    weave script 0.9.0
    weave router 0.9.0
    weave DNS 0.9.0
    weave tools 0.9.0
    

    If so the problem is that the documentation tracks current master, not the latest release – inclusion of weaveDNS status output in weave status is a post-0.9.0 feature. I’ve raised an issue to support versioning of docs to avoid this problem in future.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.