
Maintained by:
https://github.com/nodejs/docker-node
Where to get help:
the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow
Dockerfile linkshttps://github.com/nodejs/docker-node/blob/f***b756360aa4c4913b444b591b69dd8fbd8b/25/alpine3.22/Dockerfile
https://github.com/nodejs/docker-node/blob/f***b756360aa4c4913b444b591b69dd8fbd8b/25/alpine3.23/Dockerfile
https://github.com/nodejs/docker-node/blob/f***b756360aa4c4913b444b591b69dd8fbd8b/25/bookworm/Dockerfile
https://github.com/nodejs/docker-node/blob/f***b756360aa4c4913b444b591b69dd8fbd8b/25/bookworm-slim/Dockerfile
https://github.com/nodejs/docker-node/blob/f***b756360aa4c4913b444b591b69dd8fbd8b/25/bullseye/Dockerfile
https://github.com/nodejs/docker-node/blob/f***b756360aa4c4913b444b591b69dd8fbd8b/25/bullseye-slim/Dockerfile
https://github.com/nodejs/docker-node/blob/f***b756360aa4c4913b444b591b69dd8fbd8b/25/trixie/Dockerfile
https://github.com/nodejs/docker-node/blob/f***b756360aa4c4913b444b591b69dd8fbd8b/25/trixie-slim/Dockerfile
https://github.com/nodejs/docker-node/blob/58635ae7aaeab55a5c036b59e8ca93d864119cbe/24/alpine3.22/Dockerfile
https://github.com/nodejs/docker-node/blob/58635ae7aaeab55a5c036b59e8ca93d864119cbe/24/alpine3.23/Dockerfile
https://github.com/nodejs/docker-node/blob/58635ae7aaeab55a5c036b59e8ca93d864119cbe/24/bookworm/Dockerfile
https://github.com/nodejs/docker-node/blob/58635ae7aaeab55a5c036b59e8ca93d864119cbe/24/bookworm-slim/Dockerfile
https://github.com/nodejs/docker-node/blob/58635ae7aaeab55a5c036b59e8ca93d864119cbe/24/bullseye/Dockerfile
https://github.com/nodejs/docker-node/blob/58635ae7aaeab55a5c036b59e8ca93d864119cbe/24/bullseye-slim/Dockerfile
https://github.com/nodejs/docker-node/blob/58635ae7aaeab55a5c036b59e8ca93d864119cbe/24/trixie/Dockerfile
https://github.com/nodejs/docker-node/blob/58635ae7aaeab55a5c036b59e8ca93d864119cbe/24/trixie-slim/Dockerfile
https://github.com/nodejs/docker-node/blob/0001669cfeee81ddd41a0a16be9321e8a1bf2354/22/alpine3.22/Dockerfile
https://github.com/nodejs/docker-node/blob/0001669cfeee81ddd41a0a16be9321e8a1bf2354/22/alpine3.23/Dockerfile
https://github.com/nodejs/docker-node/blob/8e93bb03443b68eccbddc0f1e31a5e9756f7e70e/22/bookworm/Dockerfile
https://github.com/nodejs/docker-node/blob/8e93bb03443b68eccbddc0f1e31a5e9756f7e70e/22/bookworm-slim/Dockerfile
https://github.com/nodejs/docker-node/blob/8e93bb03443b68eccbddc0f1e31a5e9756f7e70e/22/bullseye/Dockerfile
https://github.com/nodejs/docker-node/blob/8e93bb03443b68eccbddc0f1e31a5e9756f7e70e/22/bullseye-slim/Dockerfile
https://github.com/nodejs/docker-node/blob/8e93bb03443b68eccbddc0f1e31a5e9756f7e70e/22/trixie/Dockerfile
https://github.com/nodejs/docker-node/blob/8e93bb03443b68eccbddc0f1e31a5e9756f7e70e/22/trixie-slim/Dockerfile
https://github.com/nodejs/docker-node/blob/0001669cfeee81ddd41a0a16be9321e8a1bf2354/20/alpine3.22/Dockerfile
https://github.com/nodejs/docker-node/blob/0001669cfeee81ddd41a0a16be9321e8a1bf2354/20/alpine3.23/Dockerfile
https://github.com/nodejs/docker-node/blob/8e93bb03443b68eccbddc0f1e31a5e9756f7e70e/20/bookworm/Dockerfile
https://github.com/nodejs/docker-node/blob/8e93bb03443b68eccbddc0f1e31a5e9756f7e70e/20/bookworm-slim/Dockerfile
https://github.com/nodejs/docker-node/blob/8e93bb03443b68eccbddc0f1e31a5e9756f7e70e/20/bullseye/Dockerfile
https://github.com/nodejs/docker-node/blob/8e93bb03443b68eccbddc0f1e31a5e9756f7e70e/20/bullseye-slim/Dockerfile
https://github.com/nodejs/docker-node/blob/8e93bb03443b68eccbddc0f1e31a5e9756f7e70e/20/trixie/Dockerfile
https://github.com/nodejs/docker-node/blob/8e93bb03443b68eccbddc0f1e31a5e9756f7e70e/20/trixie-slim/Dockerfile
Where to file issues:
https://github.com/nodejs/docker-node/issues?q=
Supported architectures: (https://github.com/docker-library/official-images#architectures-other-than-amd64)
https://hub.docker.com/r/amd64/node/, https://hub.docker.com/r/arm32v6/node/, https://hub.docker.com/r/arm32v7/node/, https://hub.docker.com/r/arm64v8/node/, https://hub.docker.com/r/ppc64le/node/, https://hub.docker.com/r/s390x/node/
Published image artifact details:
https://github.com/docker-library/repo-info/blob/master/repos/node (https://github.com/docker-library/repo-info/commits/master/repos/node)
(image metadata, transfer size, etc)
Image updates:
https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fnode
https://github.com/docker-library/official-images/blob/master/library/node (https://github.com/docker-library/official-images/commits/master/library/node)
Source of this description:
https://github.com/docker-library/docs/tree/master/node (https://github.com/docker-library/docs/commits/master/node)
Node.js is a software platform for scalable server-side and networking applications. Node.js applications are written in JavaScript and can be run within the Node.js runtime on Mac OS X, Windows, and Linux without changes.
Node.js applications are designed to maximize throughput and efficiency, using non-blocking I/O and asynchronous events. Node.js applications run single-threaded, although Node.js uses multiple threads for file and network events. Node.js is commonly used for real-time applications due to its asynchronous nature.
Node.js internally uses the Google V8 JavaScript engine to execute code; a large percentage of the basic modules are written in JavaScript. Node.js contains a built-in, asynchronous I/O library for file, socket, and HTTP communication. The HTTP and socket support allows Node.js to act as a web server without additional software such as Apache.
***.org/wiki/Node.js
!https://raw.githubusercontent.com/docker-library/docs/01c***b2fe592c1f93a13b4e289ada0e3a1/node/logo.png
See https://github.com/nodejs/docker-node/blob/master/README.md#how-to-use-this-image on GitHub for up-to-date documentation.
The node images come in many flavors, each designed for a specific use case.
node:<version>This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
Some of these tags may have names like bookworm, bullseye, or trixie in them. These are the suite code names for releases of Debian and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
This tag is based off of https://hub.docker.com/_/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:<version>-alpineThis image is based on the popular Alpine Linux project, available in https://hub.docker.com/_/alpine. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is useful when final image size being as small as possible is your primary concern. The main caveat to note is that it does use musl libc instead of glibc and friends, so software will often run into issues depending on the depth of their libc requirements/assumptions. 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.
To minimize image size, it's uncommon for additional related tools (such as git or bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the https://hub.docker.com/_/alpine/ for examples of how to install packages if you are unfamiliar).
node:<version>-slimThis image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run node. Unless you are working in an environment where only the node image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
View https://github.com/nodejs/node/blob/master/LICENSE for Node.js or https://github.com/nodejs/docker-node/blob/master/LICENSE for the Node.js Docker project.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in https://github.com/docker-library/repo-info/tree/master/repos/node.
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.
以下是 node 相关的常用 Docker 镜像,适用于 Web 开发、API 服务、实时应用 等不同场景:
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
无需登录使用专属域名
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
Harbor Proxy Repository 对接专属域名
Portainer Registries 加速拉取
Nexus3 Docker Proxy 内网缓存
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
docker search 限制
站内搜不到镜像
离线 save/load
插件要用 plugin install
WSL 拉取慢
安全与 digest
新手拉取配置
镜像合规机制
manifest unknown
no matching manifest(架构)
invalid tar header(解压)
TLS 证书失败
DNS 超时
域名连通性排查
410 Gone 排查
402 与流量用尽
401 认证失败
429 限流
D-Bus 凭证提示
413 与超大单层
来自真实用户的反馈,见证轩辕镜像的优质服务