yarn erroring when run from Dockerfile

[nealstewart]

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

When running yarn inside of a Dockerfile, it is

If the current behavior is a bug, please provide the steps to reproduce.

Create a Dockerfile along these lines

FROM node:4.5.0
WORKDIR /opt/my-app
RUN npm install -g yarn
ADD package.json /opt/my-app/
ADD yarn.lock /opt/my-app/
RUN yarn

This spits out an error:

error https://registry.yarnpkg.com/forever/-/forever-0.15.2.tgz: EINVAL: invalid argument, chown '/root/.yarn-cache/npm-forever-0.15.2/package.json'
    at Error (native)

What is the expected behavior?

yarn installing inside of the Docker image

Please mention your node.js, yarn and operating system version.

Node 4.5, yarn 0.15.1, Ubuntu 12.04 (Precise) on Circle CI

[cmwd]

@nealstewart have you tried to install yarn via script ?

RUN curl -o- -L https://yarnpkg.com/install.sh | bash
...
RUN $HOME/.yarn/bin/yarn install

This works for me ;)

I'm using node 6.6.0.

[Daniel15]

Try using the Ubuntu package or the install script (as @cmwd mentioned) rather than npm. Installing via npm is not reliable 100% of the time. Details are at https://yarnpkg.com/en/docs/install. For old Ubuntu versions, you'll need to add the NodeSource repo to get a recent enough version of Node.js.

Ubuntu 12.04 (Precise)

That's a very old Ubuntu version 😮

[tristanbes]

its travis year. All container-infrastructure on travis runs on unbutu 12.04 /cc @Daniel15

[Daniel15]

Ubuntu 12.04 is super old (original release was April 2012) and will be unsupported from April next year, so if Travis are using it then I really hope they upgrade soon 😛

In any case, the Yarn packages should work on 12.04 as long as you have a supported Node.js version.

[mfornasa]

If you're running Alpine containers the install script is not going to work. You can install using the tarball as I did here: https://medium.com/@mfornasa/using-yarn-with-docker-c116ad289d56

[kop]

Having a problem with Docker builds too (image is based on Alpine):

Step 6 : RUN yarn global add nodemon
 ---> Running in aba54ec6f9f4
yarn global v0.16.0
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occured, please open a bug report with the information provided in "/root/.yarn-config/global/yarn-error.log".

But since build is done in container, I can't really get "/root/.yarn-config/global/yarn-error.log" contents.
I think Yarn is definitely missing some verbose logging settings.

[mfornasa]

@kop You can extract the file from the image with docker cp

[kop]

@mfornasa, you are right totally forgot about this.

I've found this (yarn-error.log):

Arguments: 
  /usr/bin/node /opt/yarn/bin/yarn.js global add nodemon

PATH: 
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/yarn/bin

Yarn version: 
  0.16.0

Node version: 
  6.2.0

Platform: 
  linux x64

npm manifest: 
  No manifest

yarn manifest: 
  No manifest

bower manifest: 
  No manifest

Lockfile: 
  No lockfile

Trace: 
  Error: https://registry.yarnpkg.com/ps-tree/-/ps-tree-1.1.0.tgz: EINVAL: invalid argument, chown '/root/.yarn-cache/npm-ps-tree-1.1.0/package.json'
      at Error (native)

The interesting detail is that this build is passing when I'm running it from my local system (Ubuntu 16.04, Docker 1.12.2), but fails inside the CircleCI (Ubuntu 14.04, Docker 1.9.1).

[laggingreflex]

I'm having a similar problem, except for me yarn gets stuck

...
Step 6 : RUN $HOME/.yarn/bin/yarn
 ---> Running in 3f12350ceae0
yarn install v0.16.0
info No lockfile found.

Nothing happens after that. I've tried both the npm i -g yarn and the curl method of install, it just gets stuck there and nothing happens.

[oshalygin]

Using @cmwd script successfully. Pretty smooth, just takes a ton of time to install yarn as well as the packages. Going to try to optimize in the near future.

Keeping subscribed to the thread.

[Daniel15]

Pretty smooth, just takes a ton of time to install yarn

This should only happen the first time - Docker will cache the layer so future runs shouldn't have to install Yarn again (it'll used the cached version)

[oshalygin]

@Daniel15 good call, the second time was super fast.