Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install fails for unknown reasons, not enough debug output, repro steps available with minimal scenario #17499

Closed
alcohol opened this issue Dec 6, 2017 · 3 comments

Comments

@alcohol
Copy link

alcohol commented Dec 6, 2017

Version:

/workspace # node --version
v8.9.1
/workspace # npm --version
5.5.1

Platform:

  • Host
uname -a
Darwin macbookpro.local 17.2.0 Darwin Kernel Version 17.2.0: Fri Sep 29 18:27:05 PDT 2017;
  root:xnu-4570.20.62~3/RELEASE_X86_64 x86_64 i386 MacBookPro11,4 Darwin
  • Container
uname -a
Linux 0dc025d60b1c 4.9.60-linuxkit-aufs #1 SMP Mon Nov 6 16:00:12 UTC 2017 x86_64 Linux

FILES

package.json for reproduction:

{
  "name": "test",
  "private": true,
  "devDependencies": {
    "cucumber": "^2.3.1",
    "cucumber-junit": "^1.7.0"
  }
}

Dockerfile for reproduction:

FROM alpine:3.7

RUN apk add --no-cache --update git tini nodejs=8.9.1-r0

WORKDIR /workspace

ENTRYPOINT ["/sbin/tini", "--"]

REPRO

Repro steps host:

docker build --tag test-image .
docker run --rm -it -e HOME=/tmp -w /workspace -v $(pwd):/workspace test-image sh

Repro steps inside container:

npm install --verbose

OUTCOME

npm info it worked if it ends with ok
npm verb cli [ '/usr/bin/node', '/usr/bin/npm', 'install', '--verbose' ]
npm info using npm@5.5.1
npm info using node@v8.9.1
npm verb npm-session 8b372084f9346ee1
npm info lifecycle test@~preinstall: test@
npm http fetch GET 200 https://registry.npmjs.org/cucumber 128ms

...snipped...

npm info linkStuff cucumber@2.3.1
npm verb linkBins cucumber@2.3.1
npm verb linkBins [ { 'cucumber.js': './bin/cucumber.js',
npm verb linkBins     'cucumber-js': './bin/cucumber.js',
npm verb linkBins     cucumberjs: './bin/cucumber.js' },
npm verb linkBins   '/workspace/node_modules/.bin',
npm verb linkBins   false ]
npm verb linkMans cucumber@2.3.1
npm verb unlock done using /tmp/.npm/_locks/staging-afa1b9ac6beb89c7.lock for /workspace/node_modules/.staging
npm verb stack Error: ENOENT: no such file or directory, chmod '/workspace/node_modules/cucumber/bin/cucumber.js'
npm verb cwd /workspace
npm verb Linux 4.9.60-linuxkit-aufs
npm verb argv "/usr/bin/node" "/usr/bin/npm" "install" "--verbose"
npm verb node v8.9.1
npm verb npm  v5.5.1
npm ERR! path /workspace/node_modules/cucumber/bin/cucumber.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/workspace/node_modules/cucumber/bin/cucumber.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm verb exit [ -2, true ]

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/.npm/_logs/2017-12-06T16_40_19_127Z-debug.log

EXPECTED

Everything gets installed.

@cjihrig
Copy link
Contributor

cjihrig commented Dec 6, 2017

This issue tracker is for reporting bugs and feature requests related to Node core. Can you ask support questions at https://github.com/nodejs/help. Or, if you think this is an issue with npm, at https://github.com/npm/npm.

@cjihrig cjihrig closed this as completed Dec 6, 2017
@alcohol
Copy link
Author

alcohol commented Dec 6, 2017

Sorry, I don't understand the javascript ecosystem it seems.

@cjihrig
Copy link
Contributor

cjihrig commented Dec 6, 2017

No worries. Neither do I.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants