node-red

packaged by Chainguard

Chainguard Container for node-red

A minimal, Wolfi-based image for Node-RED, a low-code programming tool for wiring together hardware devices, APIs, and online services

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/node-red:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

Chainguard's Node-RED image is comparable to the upstream nodered/node-red image and is designed to be a drop-in replacement for it. It keeps the same entrypoint, node-red user, and /data user directory, so existing upstream volumes and Compose files keep working. It differs from upstream in a few ways:

• latest and the version tags include the build toolchain so nodes with native addons compile at runtime, like upstream's default tags. The -minimal tags omit it, like upstream's, and the -dev tags add the apk package manager.
• The image is built on glibc rather than Alpine's musl, so native-addon nodes compiled by the upstream image must be rebuilt, for example with npm rebuild in /data.
• There is no built-in HEALTHCHECK. Add it in your runtime, as shown in the Compose example below.
• /etc/ssh/ssh_known_hosts is not included. To use git-backed projects over SSH, mount your own.

Getting Started

Create a volume for your flows and run Node-RED, as in the upstream Docker guide:

docker volume create node_red_data
docker run -d -p 1880:1880 -v node_red_data:/data --name mynodered cgr.dev/ORGANIZATION/node-red:latest

Open http://localhost:1880 to use the editor. Flows and installed nodes are stored in the volume, so they survive removing and recreating the container.

To run it with Docker Compose and the upstream healthcheck, create a compose.yaml:

cat > compose.yaml <<EOF
services:
  node-red:
    image: cgr.dev/ORGANIZATION/node-red:latest
    ports:
      - "1880:1880"
    volumes:
      - node_red_data:/data
    healthcheck:
      test: ["CMD", "node", "/healthcheck.js"]
      interval: 30s
      timeout: 10s
      start_period: 30s
volumes:
  node_red_data:
EOF
docker compose up -d

Documentation and Resources

• Node-RED documentation
• Node-RED runtime configuration
• Running Node-RED under Docker
• Node-RED GitHub repository
• node-red-docker GitHub repository
• Chainguard Containers migration guide

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.