Skip to content

Instantly share code, notes, and snippets.

@marzzz21
Created March 17, 2017 03:26
Show Gist options
  • Save marzzz21/834cec8730e04a1ba2aae17e6a6002e9 to your computer and use it in GitHub Desktop.
Save marzzz21/834cec8730e04a1ba2aae17e6a6002e9 to your computer and use it in GitHub Desktop.
Sending build context to Docker daemon 57.34 kB
Step 1/17 : FROM ubuntu
---> 0ef2e08ed3fa
Step 2/17 : RUN apt-get update
---> Using cache
---> b474bce9606e
Step 3/17 : RUN apt-get -y install curl vim
---> Using cache
---> a439ce1f5ec0
Step 4/17 : RUN curl -LO https://nodejs.org/dist/v4.1.2/node-v4.1.2-linux-x64.tar.gz && tar zxvf node-v4.1.2-linux-x64.tar.gz && /bin/bash -c "cp -a node-v4.1.2-linux-x64/{bin,include,lib,share} /usr" && rm node-v4.1.2-linux-x64.tar.gz
---> Using cache
---> 8abb71700616
Step 5/17 : RUN useradd -ms /bin/bash hubot
---> Using cache
---> 2427955f5df3
Step 6/17 : RUN npm install -g npm
---> Running in d0dd11d5f7d8
npm ERR! Linux 3.10.0-514.6.1.el7.x86_64
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "npm"
npm ERR! node v4.1.2
npm ERR! npm v2.14.4
npm ERR! path /usr/lib/node_modules/npm/scripts
npm ERR! code ENOTEMPTY
npm ERR! errno -39
npm ERR! syscall rmdir
npm ERR! ENOTEMPTY: directory not empty, rmdir '/usr/lib/node_modules/npm/scripts'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! error rolling back Error: ENOTEMPTY: directory not empty, rmdir '/usr/lib/node_modules/npm/scripts'
npm ERR! error rolling back at Error (native)
npm ERR! error rolling back { [Error: ENOTEMPTY: directory not empty, rmdir '/usr/lib/node_modules/npm/scripts']
npm ERR! error rolling back errno: -39,
npm ERR! error rolling back code: 'ENOTEMPTY',
npm ERR! error rolling back syscall: 'rmdir',
npm ERR! error rolling back path: '/usr/lib/node_modules/npm/scripts' }
npm ERR! Please include the following file with any support request:
npm ERR! /npm-debug.log
The command '/bin/sh -c npm install -g npm' returned a non-zero code: 217
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment