← All tasks
javascriptyarnpkg/yarn #2629Not checked yet

yarn install fails with `ENOENT: no such file or directory` occasionally

envgap__yarnpkg__yarn-2629

Original GitHub issue ↗Opened 2017-02-04

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.
Not checked yet.
  • No curated issue-specific recipe or verified environment fix is available.

02 / ENVIRONMENT RECIPE

Base commit
Not freshly verified
Manifest
package.json
Reproduce
Awaiting issue-specific recipe
Run under trace
Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

yarnpkg/yarn #2629 · read the original issue
Running `yarn install` as part of a build step for a [Docker image](https://github.com/NiGhTTraX/react-test-buffet/blob/85749bb75e7d7ada08419eff377b0f02e88a94dd/Dockerfile#L1) based on `node:7` [fails on Travis CI](https://travis-ci.org/NiGhTTraX/react-test-buffet/builds/198314605#L384) with `ENOTEMPTY`, `EEXISTS` errors. It always seems to error on the `webdriverio` package.



```

yarn install v0.19.1

[1/4] Resolving packages...

[2/4] Fetching packages...

error An unexpected error occurred: "https://registry.yarnpkg.com/webdriverio/-/webdriverio-4.6.2.tgz: ENOENT: no such file or directory, open '/usr/local/share/.cache/yarn/npm-webdriverio-4.6.2-dd095ee618896a21c8f1b9d4278736d85a64ca0f/lib/protocol/timeouts.js'".

```



When Travis runs `yarn install` as part of the install phase it [works just fine](https://travis-ci.org/NiGhTTraX/react-test-buffet/builds/198314605#L253). The error only happens when building a Docker image.



[Repo](https://github.com/NiGhTTraX/react-test-buffet/tree/85749bb75e7d7ada08419eff377b0f02e88a94dd) which reproduces this issue.



node:7

OS: Docker + Travis CI

yarn: 0.19.1

[package.json](https://github.com/NiGhTTraX/react-test-buffet/blob/85749bb75e7d7ada08419eff377b0f02e88a94dd/package.json)

[yarn.lock](https://github.com/NiGhTTraX/react-test-buffet/blob/85749bb75e7d7ada08419eff377b0f02e88a94dd/yarn.lock)



I've tried installing yarn both with `npm install -g` and with `apt` and both methods cause the failure on Travis.



Weirdly enough, the image builds successfully on my local machine which runs Ubuntu 16.04.1 LTS with Docker version 1.13.0, build 49bf474.
Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched
[]

Issue-specific recipe and runtime smoke command require review against the complete issue and repository.

Legacy already_works is install-only; proposed control still requires runtime verification.