Expected behavior
After switching wireless networks, network / DNS requests should succeed when building an image.
Actual behavior
Errors:
$ docker-compose build
Building web
Step 1 : FROM atomiq/node:onbuild
# Executing 3 build triggers...
Step 1 : COPY package.json /usr/src/app/
Step 1 : RUN npm install --loglevel error ### -- THIS WILL TAKE A WHILE! Go get some coffee. -- ###
---> Running in 50730e122d50
npm ERR! Linux 4.4.6
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--loglevel" "error"
npm ERR! node v5.8.0
npm ERR! npm v3.7.3
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! syscall getaddrinfo
npm ERR! network getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Please include the following file with any support request:
npm ERR! /usr/src/app/npm-debug.log
ERROR: Service 'web' failed to build: The command '/bin/sh -c npm install --loglevel error ' returned a non-zero code: 1
Information
- the output of:
-
pinata diagnose -u
on OSX
-
OS X: version 10.11.3 (build: 15D21)
Docker.app: version v1.11.0-beta7
Running diagnostic tests:
[OK] docker-cli
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160418-062304.tar.gz
Most specific failure is: No error was detected
Your unique id is: 537EFDB5-67ED-4BAF-8982-9A848BE93025
Please quote this in all correspondence.
- host distribution and version ( OSX 10.10.x, OSX 10.11.x, Windows, etc )
OSX 10.11.3
Steps to reproduce the behavior
- Switch wireless network
Notes
This happens frequently. The solution is to restart the Docker daemon. This issue is not specific to Docker for Mac beta (it happens with Docker Machine as well).