| Sep | OCT | Nov |
| 23 | ||
| 2019 | 2020 | 2021 |
COLLECTED BY
Collection: github.com
feat: upgrade to node 15.0.14b70c53
Dockerfile in your Node.js app project
●Best Practices
●Run a single Node.js script
●Verbosity
●Dockerfile
●Docker Run
●NPM run
●Image Variants
●node:<version>
●node:alpine
●node:slim
●License
●Supported Docker versions
●Supported Node.js versions
●Governance and Current Members
●Docker Working Group Members
●Docker Working Group Collaborators
●Emeritus
●Docker Working Group Members
Dockerfile in your Node.js app project
# specify the node base image with your desired version node:<version> FROM node:10 # replace this with your application's default port EXPOSE 8888You can then build and run the Docker image:
$ docker build -t my-nodejs-app . $ docker run -it --rm --name my-running-app my-nodejs-appIf you prefer Docker Compose:
version: "2" services: node: image: "node:8" user: "node" working_dir: /home/node/app environment: - NODE_ENV=production volumes: - ./:/home/node/app expose: - "8081" command: "npm start"You can then run using Docker Compose:
$ docker-compose up -d
Docker Compose example copies your current directory (including node_modules) to the container.
It assumes that your application has a file named package.json
defining start script.
Dockerfile. In such cases, you can run a Node.js script by using the
Node.js Docker image directly:
$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/app -w /usr/src/app node:8 node your-daemon-or-script.js
warntoinfo. However due to improvements to npm and new Docker
patterns (e.g. multi-stage builds) the working group reached a consensus
to revert the log level to npm defaults. If you need more verbose output, please
use one of the following methods to change the verbosity level.
Dockerfile which inherits from the node image you can
simply use ENV to override NPM_CONFIG_LOGLEVEL.
FROM node ENV NPM_CONFIG_LOGLEVEL info ...
docker run you can use the -e flag to
override NPM_CONFIG_LOGLEVEL.
$ docker run -e NPM_CONFIG_LOGLEVEL=info node ...
--loglevel to control the
verbosity of the output.
$ docker run node npm --loglevel=warn ...
node images come in many flavors, each designed for a specific use case.
All of the images contain pre-installed versions of node,
npm, and yarn. For each
supported architecture, the supported variants are different. In the file:
architectures, it lists all supported variants for all of
the architectures that we support now.
node:<version>
buildpack-deps.
buildpack-deps is designed for the average user of docker who has many images
on their system. It, by design, has a large number of extremely common Debian
packages. This reduces the number of packages that images that derive from it
need to install, thus reducing the overall size of all images on your system.
node:alpine
alpine official image. Alpine Linux is
much smaller than most distribution base images (~5MB), and thus leads to much
slimmer images in general.
This variant is highly recommended when final image size being as small as
possible is desired. The main caveat to note is that it does use
musl libc instead of
glibc and friends, so certain
software might run into issues depending on the depth of their libc
requirements. However, most software doesn't have an issue with this, so this
variant is usually a very safe choice. See
this Hacker News comment thread
for more discussion of the issues that might arise and some pro/con comparisons
of using Alpine-based images. One common issue that may arise is a missing shared
library required for use of process.dlopen. To add the missing shared libraries
to your image, adding the libc6-compat
package in your Dockerfile is recommended: apk add --no-cache libc6-compat
To minimize image size, it's uncommon for additional related tools
(such as gitorbash) to be included in Alpine-based images. Using this
image as a base, add the things you need in your own Dockerfile
(see the alpine image description for
examples of how to install packages if you are unfamiliar).
node:slim
node. Unless you are working
in an environment where only the Node.js image will be deployed and you have
space constraints, we highly recommend using the default image of this
repository.