The issue is solved upstream https://github.com/docker/docker/issues/541 and can be circumvented on older version of Docker using this help https://docs.docker.com/installation/ubuntulinux/#docker-and-local-dns-server-warnings
Jan On Wed, 3 Sep 2014 10:44:46 +0200 Jan Blechta <[email protected]> wrote: > When going through these instructions > https://bitbucket.org/garth-wells/fenics-virtual/src/16d94547b6c081c47c2b491da52cdba1273b5a4d/vagrant/docker-dev/README.md?at=vagrant-docker > (I installed docker, vagrant previously when using > https://bitbucket.org/lzlarryli/fenics_via_vagrant/src/master/dev/) > I get > > ========================================================= > fenics@da3b8d60e598:~$ update_fenics > FENICS-BUILDER: Pulling ffc... > -bash: cd: /opt/fenics-dev/src: No such file or directory > Cloning into 'ffc'... > fatal: unable to access > 'https://bitbucket.org/fenics-project/ffc.git/': Could not resolve > host: bitbucket.org -bash: cd: ffc: No such file or directory > ========================================================= > > It seems like DNS name bitbucket.org can't be resolved for some reason > > fenics@da3b8d60e598:~$ping bitbucket.org > ping: unknown host bitbucket.org > > while pinging bitbucket's IP (obtained by host command on host > machine) directly works. > > Which information should I provide to trace the problem? > > Jan > _______________________________________________ > fenics-support mailing list > [email protected] > http://fenicsproject.org/mailman/listinfo/fenics-support _______________________________________________ fenics-support mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics-support
