Bitnami 提供的 Node.js 安全镜像,基于 Photon Linux 构建,具有强化安全特性、最小漏洞、合规支持和供应链安全保障,适用于快速部署安全可靠的 Node.js 应用。
Bitnami Secure Image for Node.js
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.
https://nodejs.org/ 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.
TL;DR
consoledocker run --name node REGISTRY_NAME/bitnami/node:latest
Note: You need to substitute the
REGISTRY_NAMEplaceholder with a reference to your container registry.
Choosing between the Standard and Minimal image
This asset is available in two flavors: Standard and Minimal; designed to address different use cases and operational needs.
Standard images
The standard images are full-featured, production-ready containers built on top of secure base operating systems. They include:
- The complete runtime and commonly used system tools.
- A familiar Linux environment (shell, package manager, debugging utilities).
- Full compatibility with most CI/CD pipelines and existing workloads.
Recommended for:
- Development and testing environments.
- Workloads requiring package installation or debugging tools.
- Applications that depend on system utilities or shared libraries.
Minimal images
The minimal images are optimized, distroless-style containers derived from a stripped-down base. They only ship what’s strictly necessary to run the application; no shell, package manager, or extra libraries. They provide:
- Smaller size: Faster pull and startup times.
- Reduced *** surface: Fewer components and potential vulnerabilities.
- Simpler maintenance: Fewer dependencies to patch or update.
Recommended for:
- Production environments prioritizing performance and security.
- Regulated or security-sensitive workloads
- Containers built via multi-stage builds (e.g., Golang static binaries).
Supported tags and respective Dockerfile links
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html.
Get this image
The Bitnami Node.js Docker image is only available to https://bitnami.com customers.
Entering the REPL
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.
consoledocker run -it --name node bitnami/node
Further Reading:
- https://nodejs.org/api/repl.html
Configuration
The following section describes how to run commands
Running your Node.js script
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.
consoledocker run -it --name node -v /path/to/app:/app bitnami/node \ node script.js
Running a Node.js app with npm dependencies
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.
consoledocker 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
Further Reading:
- https://docs.npmjs.com/files/package.json
- https://docs.npmjs.com/misc/scripts#default-values
FIPS configuration in Bitnami Secure Images
The Bitnami Node.js Docker image from the https://go-vmware.broadcom.com/contact-us catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:
OPENSSL_FIPS: whether OpenSSL runs in FIPS mode or not.yes(default),no.
Working with private npm modules
To work with npm private modules, it is necessary to be logged into npm. npm CLI uses auth tokens for authentication. Check the official https://www.npmjs.com/package/get-npm-token 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
npmrcfile within the project. It contains the instructions for thenpmcommand to authenticate against npmjs.org registry. TheNPM_TOKENwill be taken at build time. The file should look like this:
console//registry.npmjs.org/:_authToken=${NPM_TOKEN}
- Add some new lines to the Dockerfile in order to copy the
npmrcfile, add the expectedNPM_TOKENby using the ARG parameter, and remove thenpmrcfile once the npm install is completed.
You can find the Dockerfile below:
dockerfileFROM 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 buildcommand as follows:
consoledocker 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
- https://docs.npmjs.com/private-modules/docker-and-private-modules.
Accessing a Node.js app running a web server
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 http://expressjs.com/ app listening to remote connections on port 3000:
javascriptvar 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.
consoledocker 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.
console$ 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.
consoledocker 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.
Connecting to other containers
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.
Serving your Node.js app through an nginx frontend
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.
Step 1: Create a network
consoledocker network create app-tier --driver bridge
Step 2: Create a virtual host
Let's create an nginx virtual host to reverse proxy to our Node.js container.
nginxserver { 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.
Step 3: Run the Node.js image with a specific name
consoledocker run -it --name myapp --network app-tier \ -v /path/to/app:/app \ bitnami/node node index.js
Step 4: Run the nginx image
consoledocker run -it \ -v /path/to/vhost.conf:/bitnami/nginx/conf/vhosts/yourapp.conf:ro \ --network app-tier \ bitnami/nginx
Notable Changes
Starting January 16, 2024
- The
docker-compose.yamlfile has been removed, as it was solely intended for internal testing purposes.
6.2.0-r0 (2016-05-11)
- Commands are now executed as the
rootuser. Use the--userargument to switch to another user or change to the required user usingsudoto launch applications. Alternatively, as of Docker 1.10 User Namespaces are supported by the docker daemon. Refer to the https://docs.docker.com/engine/security/userns-remap/ for more details.
4.1.2-0 (2015-10-12)
- Permissions fixed so
bitnamiuser can install global npm modules without needingsudo.
4.1.1-0-r01 (2015-10-07)
/appdirectory 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 DockerfileRUNinstructions. To keep the previous behavior (so that you can mount the volume in another container), create the container with the-v /appoption.
License
Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.
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.
更多相关 Docker 镜像与资源
以下是 bitnami/node 相关的常用 Docker 镜像,适用于 Web 开发、API 服务、实时应用 等不同场景:
镜像拉取方式
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。
DockerHub 原生拉取命令
用户好评
来自真实用户的反馈,见证轩辕镜像的优质服务