Looks like moving sudoroom-data outside the source dir broke the docker instructions.
> sudo-humans@0.0.0 start /usr/src/app
> bin/cmd.js
/usr/src/app/node_modules/mkdirp/index.js:90
throw err0;
^
Error: EEXIST, file already exists '/usr/src/app/sudoroom-data'
at Object.fs.mkdirSync (fs.js:651:18)
at sync (/usr/src/app/node_modules/mkdirp/index.js:71:13)
at Function.sync (/usr/src/app/node_modules/mkdirp/index.js:77:24)
at Object.<anonymous> (/usr/src/app/bin/cmd.js:101:8)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
npm ERR! Linux 4.4.0-66-generic
npm ERR! argv "node" "/usr/local/bin/npm" "start"
npm ERR! node v0.10.29
npm ERR! npm v3.10.9
npm ERR! code ELIFECYCLE
npm ERR! sudo-humans@0.0.0 start: `bin/cmd.js`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the sudo-humans@0.0.0 start script 'bin/cmd.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the sudo-humans package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! bin/cmd.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs sudo-humans
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls sudo-humans
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /usr/src/app/npm-debug.log
Looks like moving sudoroom-data outside the source dir broke the docker instructions.
Oops.