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

A new problem with yarn has cropped up #651

Closed
richtera opened this issue Mar 16, 2018 · 10 comments
Closed

A new problem with yarn has cropped up #651

richtera opened this issue Mar 16, 2018 · 10 comments

Comments

@richtera
Copy link

When using the plain node:8 or node:9 docker using npm install -g yarn no longer works. There is some kind of left over link in /usr/local/bin/yarn but no complete yarn install. So you get an error

npm ERR! path /usr/local/bin/yarnpkg
npm ERR! code EEXIST
npm ERR! Refusing to delete /usr/local/bin/yarnpkg: /opt/yarn/bin/yarn symlink target is not controlled by npm /usr/local/bin
npm ERR! File exists: /usr/local/bin/yarnpkg
npm ERR! Move it away, and try again.

But executing

if which yarn; then
  echo "Yarn is installed!"
else
  echo "Yarn is not installed :-("
fi

shows yarn is not installed.
Thanks
Andy

@MichaelRBond
Copy link

Also seeing this in node:carbon-slim

@chorrell
Copy link
Contributor

This looks like it was related to the #647 and #648 changes.

This should (finally) be fixed in #650. So far my local testing of npm install -g yarn and which yarn of the changes in #650 seem to be ok

@conradob
Copy link

As workaround I implemented the specific node image version
To FROM node:6.13.0 from FROM node:boron

just need to downgrade one version

@dahlb
Copy link

dahlb commented Mar 16, 2018

looks like the dockerfile is adding && mkdir -p /opt/yarn \ which is making the symbolic link command of ln -s /opt/yarn-v$YARN_VERSION /opt/yarn
generate /opt/yarn/yarn-v$YARN_VERSION instead of the intended /opt/yarn

@dahlb
Copy link

dahlb commented Mar 16, 2018

looks like reverting
63b1fa1
would fix it

@SimenB
Copy link
Member

SimenB commented Mar 16, 2018

@dahlb please see #650

@chorrell
Copy link
Contributor

chorrell commented Mar 16, 2018

Here's the docker hub PR that should resolve this:

docker-library/official-images#4137

@SimenB
Copy link
Member

SimenB commented Mar 16, 2018

Off by one char there, this is the link: docker-library/official-images#4137

@chorrell
Copy link
Contributor

ugh..thanks

@SimenB
Copy link
Member

SimenB commented Mar 16, 2018

I'll close this as well. Will reopen if it still doesn't work after that is merged and released

@SimenB SimenB closed this as completed Mar 16, 2018
pcraig3 added a commit to NRCan/energuide_api_guide that referenced this issue Mar 16, 2018
There was an upsteam issue where some node docker containers were
released without yarn.
The solution seems to be to wait until a fix is pushed.
nodejs/docker-node#651
Alternatively, there's some ENV we can maybe set if we still
here.
pcraig3 added a commit to NRCan/energuide_api_guide that referenced this issue Mar 16, 2018
Earlier this morning, all of our builds and deploys
started mysteriously failing.
It turns out that yarn vanished from a docker container we
were using, and then lots of people's builds started failing.

Here's the relevant github issue:
 - nodejs/docker-node#651
Here's a tweet from circleci with a workaround:
 - https://twitter.com/circleci/status/974703363542495232

This workaround gives us yarn back, but it's not able to
globally install `now`, so I've installed that locally
and then am just calling the local file to run the deployment.

Got our green checkmarks back finally, so all systems go.
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

6 participants