One of the biggest obstacles to my team adopting yarn was putting together a docker image that included yarn. After doing a bunch of work i’ve determined that this very easy but non-obvious. It doesn’t help that search results return a number of individual contributions that are flawed in one way or another. Many use the npm install method which is not recommended and others use curl -o- -L https://yarnpkg.com/install.sh | bash which installs only for the current user.
Here’s my take – https://hub.docker.com/r/mattkime/node-yarn/
Let me know if there’s anything i can do to help move this forward.
@Daniel15 Extending the official node images should be sufficient. Simply because we can’t satisfy all use cases doesn’t mean we can’t satisfy most use cases.
Sure, that’s doable. I’ll add a Docker image soon when I revise the dev one👍
Now available as
yarnpkg/node-yarnin the Docker Hub: https://hub.docker.com/r/yarnpkg/node-yarn/FYI, Yarn is now part of the official Node.js Docker image: nodejs/docker-node#243. So you don’t have to use the
node-yarnimage any more.