nodejs
/
docker-node
mirror of https://github.com/nodejs/docker-node.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update README.md 

with an example on how to upgrade/downgrade yarn version
This commit is contained in:
Eyal Zekaria 2018-03-09 11:38:53 +01:00
parent 838d873498
commit 926d446701
No known key found for this signature in database
GPG Key ID: 0CA530157CF63A8E
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/BestPractices.md
View File

@ -29,6 +29,21 @@ ENV NPM_CONFIG_PREFIX=/home/node/.npm-global
ENV PATH=$PATH:/home/node/.npm-global/bin # optionally if you want to run npm global bin without specifying path
```
## Upgrading/downgrading Yarn
If you need to upgrade/downgrade `yarn`, you can do so by issuing the following commands in your `Dockerfile`:
```Dockerfile
FROM node:6
ENV YARN_VERSION 1.5.1
RUN curl -fSLO --compressed "https://yarnpkg.com/downloads/$YARN_VERSION/yarn-v$YARN_VERSION.tar.gz" \
&& tar -xzf yarn-v$YARN_VERSION.tar.gz -C /opt/ \
&& ln -snf /opt/yarn-v$YARN_VERSION /opt/yarn \
&& rm yarn-v$YARN_VERSION.tar.gz
```
## Handling Kernel Signals
Node.js was not designed to run as PID 1 which leads to unexpected behaviour when running inside of Docker. For example, a Node.js process running as PID 1 will not respond to `SIGTERM` (`CTRL-C`) and similar signals. As of Docker 1.13, you can use the `--init` flag to wrap your Node.js process with a [lightweight init system](https://github.com/krallin/tini) that properly handles running as PID 1.