Node.js is a runtime environment built on V8 JavaScript engine. Its event-driven, non-blocking I/O model enables the development of fast, scalable, and data-intensive server applications.
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
$ docker run -it --name node bitnami/node
$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-node/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d
- Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
- With Bitnami images the latest bug fixes and features are available as soon as possible.
- Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
- All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading Linux distribution.
- All Bitnami images available in Docker Hub are signed with Docker Content Trust (DCT). You can use
DOCKER_CONTENT_TRUST=1
to verify the integrity of the images. - Bitnami container images are released on a regular basis with the latest distribution packages available.
Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami Node.js Chart GitHub repository.
Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.
18
,18-debian-11
,18.4.0
,18.4.0-debian-11-r5
,latest
(18/debian-11/Dockerfile)17
,17-debian-11
,17.9.1
,17.9.1-debian-11-r11
(17/debian-11/Dockerfile)16
,16-debian-11
,16.15.1
,16.15.1-debian-11-r9
(16/debian-11/Dockerfile)14
,14-debian-11
,14.19.3
,14.19.3-debian-11-r11
(14/debian-11/Dockerfile)12
,12-debian-11
,12.22.12
,12.22.12-debian-11-r11
(12/debian-11/Dockerfile)
Subscribe to project updates by watching the bitnami/node GitHub repo.
The recommended way to get the Bitnami Node.js Docker Image is to pull the prebuilt image from the Docker Hub Registry.
$ docker pull bitnami/node:latest
To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.
$ docker pull bitnami/node:[TAG]
If you wish, you can also build the image yourself.
$ docker build -t bitnami/node 'https://github.com/bitnami/bitnami-docker-node.git#master:18/debian-11'
By default, running this image will drop you into the Node.js REPL, where you can interactively test and try things out in Node.js.
$ docker run -it --name node bitnami/node
Further Reading:
The default work directory for the Node.js image is /app
. You can mount a folder from your host here that includes your Node.js script, and run it normally using the node
command.
$ docker run -it --name node -v /path/to/app:/app bitnami/node \
node script.js
If your Node.js app has a package.json
defining your app's dependencies and start script, you can install the dependencies before running your app.
$ docker run --rm -v /path/to/app:/app bitnami/node npm install
$ docker run -it --name node -v /path/to/app:/app bitnami/node npm start
or by modifying the docker-compose.yml
file present in this repository:
node:
...
command: "sh -c 'npm install && npm start'"
volumes:
- .:/app
...
Further Reading:
To work with npm private modules, it is necessary to be logged into npm. npm CLI uses auth tokens for authentication. Check the official npm documentation for further information about how to obtain the token.
If you are working in a Docker environment, you can inject the token at build time in your Dockerfile by using the ARG parameter as follows:
- Create a
npmrc
file within the project. It contains the instructions for thenpm
command to authenticate against npmjs.org registry. TheNPM_TOKEN
will be taken at build time. The file should look like this:
//registry.npmjs.org/:_authToken=${NPM_TOKEN}
- Add some new lines to the Dockerfile in order to copy the
npmrc
file, add the expectedNPM_TOKEN
by using the ARG parameter, and remove thenpmrc
file once the npm install is completed.
You can find the Dockerfile below:
FROM bitnami/node
ARG NPM_TOKEN
COPY npmrc /root/.npmrc
COPY . /app
WORKDIR /app
RUN npm install
CMD node app.js
- Now you can build the image using the above Dockerfile and the token. Run the
docker build
command as follows:
$ docker build --build-arg NPM_TOKEN=${NPM_TOKEN} .
| NOTE: The "." at the end gives docker build
the current directory as an argument.
Congratulations! You are now logged into the npm repo.
Further reading
By default the image exposes the port 3000
of the container. You can use this port for your Node.js application server.
Below is an example of an express.js app listening to remote connections on port 3000
:
var express = require('express');
var app = express();
app.get('/', function (req, res) {
res.send('Hello World!');
});
var server = app.listen(3000, '0.0.0.0', function () {
var host = server.address().address;
var port = server.address().port;
console.log('Example app listening at http://%s:%s', host, port);
});
To access your web server from your host machine you can ask Docker to map a random port on your host to port 3000
inside the container.
$ docker run -it --name node -v /path/to/app:/app -P bitnami/node node index.js
Run docker port
to determine the random port Docker assigned.
$ docker port node
3000/tcp -> 0.0.0.0:32769
You can also specify the port you want forwarded from your host to the container.
$ docker run -it --name node -p 8080:3000 -v /path/to/app:/app bitnami/node node index.js
Access your web server in the browser by navigating to http://localhost:8080
.
If you want to connect to your Node.js web server inside another container, you can use docker networking to create a network and attach all the containers to that network.
We may want to make our Node.js web server only accessible via an nginx web server. Doing so will allow us to setup more complex configuration, serve static assets using nginx, load balance to different Node.js instances, etc.
$ docker network create app-tier --driver bridge
or using Docker Compose:
version: '2'
networks:
app-tier:
driver: bridge
Let's create an nginx virtual host to reverse proxy to our Node.js container.
server {
listen 0.0.0.0:80;
server_name yourapp.com;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header HOST $http_host;
proxy_set_header X-NginX-Proxy true;
# proxy_pass http://[your_node_container_link_alias]:3000;
proxy_pass http://myapp:3000;
proxy_redirect off;
}
}
Notice we've substituted the link alias name myapp
, we will use the same name when creating the container.
Copy the virtual host above, saving the file somewhere on your host. We will mount it as a volume in our nginx container.
$ docker run -it --name myapp --network app-tier \
-v /path/to/app:/app \
bitnami/node node index.js
or using Docker Compose:
version: '2'
myapp:
image: bitnami/node
command: node index.js
networks:
- app-tier
volumes:
- .:/app
$ docker run -it \
-v /path/to/vhost.conf:/bitnami/nginx/conf/vhosts/yourapp.conf:ro \
--network app-tier \
bitnami/nginx
or using Docker Compose:
version: '2'
nginx:
image: bitnami/nginx
networks:
- app-tier
volumes:
- /path/to/vhost.conf:/bitnami/nginx/conf/vhosts/yourapp.conf:ro
Bitnami provides up-to-date versions of Node.js, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
$ docker pull bitnami/node:latest
or if you're using Docker Compose, update the value of the image property to bitnami/node:latest
.
$ docker rm -v node
or using Docker Compose:
$ docker-compose rm -v node
Re-create your container from the new image.
$ docker run --name node bitnami/node:latest
or using Docker Compose:
$ docker-compose up node
- Commands are now executed as the
root
user. Use the--user
argument to switch to another user or change to the required user usingsudo
to launch applications. Alternatively, as of Docker 1.10 User Namespaces are supported by the docker daemon. Refer to the daemon user namespace options for more details.
- Permissions fixed so
bitnami
user can install global npm modules without needingsudo
.
/app
directory is no longer exported as a volume. This caused problems when building on top of the image, since changes in the volume are not persisted between DockerfileRUN
instructions. To keep the previous behavior (so that you can mount the volume in another container), create the container with the-v /app
option.
Node.js's branch 12 is no longer maintained by upstream and is now internally tagged as to be deprecated. This branch will no longer be released in our catalog a month after this notice is published, but already released container images will still persist in the registries. Valid to be removed starting on: 06-03-2022
Node.js's branch 17 is no longer maintained by upstream and is now internally tagged as to be deprecated. This branch will no longer be released in our catalog a month after this notice is published, but already released container images will still persist in the registries. Valid to be removed starting on: 07-04-2022
We'd love for you to contribute to this Docker image. You can request new features by creating an issue, or submit a pull request with your contribution.
If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:
- Host OS and version
- Docker version (
docker version
) - Output of
docker info
- Version of this container
- The command you used to run the container, and any relevant output you saw (masking any sensitive information)
Copyright © 2022 Bitnami
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.