8000 The "simple" docker-compose up fails with Error: ENOENT, no such file or directory '/home/node/.babel.json' · Issue #20 · sibartlett/colonizers · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
The "simple" docker-compose up fails with Error: ENOENT, no such file or directory '/home/node/.babel.json' #20
Open
@giacecco

Description

@giacecco

The simple docker-compose.yml offered in the documentation fails with the error shown below:

(...)
colonizers_1 | fs.js:0
colonizers_1 | (function (exports, require, module, __filename, __dirname) { // Copyright Joy
colonizers_1 | 
colonizers_1 | Error: ENOENT, no such file or directory '/home/node/.babel.json'
colonizers_1 |     at Error (native)
colonizers_1 |     at Object.fs.openSync (fs.js:500:18)
colonizers_1 |     at Object.fs.writeFileSync (fs.js:1099:15)
colonizers_1 |     at save (/usr/src/app/node_modules/babel-core/lib/api/register/cache.js:35:19)
colonizers_1 |     at process._tickCallback (node.js:355:11)
colonizers_1 |     at Function.Module.runMain (module.js:503:11)
colonizers_1 |     at startup (node.js:129:16)
colonizers_1 |     at node.js:814:3
colonizers_1 | 
colonizers_1 | npm ERR! Linux 4.1.18-boot2docker
colonizers_1 | npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
colonizers_1 | npm ERR! node v0.12.11
colonizers_1 | npm ERR! npm  v2.14.9
colonizers_1 | npm ERR! code ELIFECYCLE
colonizers_1 | npm ERR! colonizers@0.0.0 start: `node server/index.js`
colonizers_1 | npm ERR! Exit status 1
colonizers_1 | npm ERR! 
colonizers_1 | npm ERR! Failed at the colonizers@0.0.0 start script 'node server/index.js'.
colonizers_1 | npm ERR! This is most likely a problem with the colonizers package,
colonizers_1 | npm ERR! not with npm itself.
colonizers_1 | npm ERR! Tell the author that this fails on your system:
colonizers_1 | npm ERR!     node server/index.js
colonizers_1 | npm ERR! You can get their info via:
colonizers_1 | npm ERR!     npm owner ls colonizers
colonizers_1 | npm ERR! There is likely additional logging output above.
colonizers_1 | npm ERR! Linux 4.1.18-boot2docker
colonizers_1 | npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
colonizers_1 | npm ERR! node v0.12.11
colonizers_1 | npm ERR! npm  v2.14.9
colonizers_1 | npm ERR! path npm-debug.log.7da2e9feb6af80ea1c45d89105a542fd
colonizers_1 | npm ERR! code EACCES
colonizers_1 | npm ERR! errno -13
colonizers_1 | 
colonizers_1 | npm ERR! Error: EACCES, open 'npm-debug.log.7da2e9feb6af80ea1c45d89105a542fd'
colonizers_1 | npm ERR!     at Error (native)
colonizers_1 | npm ERR!  { [Error: EACCES, open 'npm-debug.log.7da2e9feb6af80ea1c45d89105a542fd']
colonizers_1 | npm ERR!   errno: -13,
colonizers_1 | npm ERR!   code: 'EACCES',
colonizers_1 | npm ERR!   path: 'npm-debug.log.7da2e9feb6af80ea1c45d89105a542fd' }
colonizers_1 | npm ERR! 
colonizers_1 | npm ERR! Please try running this command again as root/Administrator.
colonizers_1 | 
colonizers_1 | npm ERR! Please include the following file with any support request:
colonizers_1 | npm ERR!     /usr/src/app/npm-debug.log
docker_colonizers_1 exited with code 1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0