openclaw - 💡(How to fix) Fix Remove NodeSource pipe-to-bash in test Dockerfile [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#59031Fetched 2026-04-08 02:29:36
View on GitHub
Comments
1
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
closed ×1commented ×1locked ×1

Fix Action

Fix

This Dockerfile should use the official node:24-bookworm image (already SHA256-pinned in the main Dockerfile) instead of installing Node via NodeSource. No reason to use a separate install path.

Code Example

curl -fsSL https://deb.nodesource.com/setup_24.x | bash -
RAW_BUFFERClick to expand / collapse

Problem

scripts/docker/install-sh-nonroot/Dockerfile line 31 uses pipe-to-bash:

curl -fsSL https://deb.nodesource.com/setup_24.x | bash -

Risk

  • No checksum verification on setup script
  • Script modifies system apt sources — if NodeSource is compromised, future apt install nodejs pulls malicious packages
  • Only in test/utility Dockerfile, not production

Fix

This Dockerfile should use the official node:24-bookworm image (already SHA256-pinned in the main Dockerfile) instead of installing Node via NodeSource. No reason to use a separate install path.

Priority

Low — test utility image only, not production

🤖 Generated with Claude Code

extent analysis

TL;DR

Use the official node:24-bookworm image instead of installing Node via NodeSource in the scripts/docker/install-sh-nonroot/Dockerfile.

Guidance

  • Replace the line curl -fsSL https://deb.nodesource.com/setup_24.x | bash - with FROM node:24-bookworm to use the official Node image.
  • Verify that the Dockerfile builds correctly and the resulting image has the expected Node version.
  • Remove any unnecessary dependencies or setup scripts related to NodeSource.
  • Test the updated Dockerfile to ensure it works as expected in the test/utility environment.

Example

# Replace the existing Dockerfile content with:
FROM node:24-bookworm

Notes

This fix only applies to the scripts/docker/install-sh-nonroot/Dockerfile and does not affect the production environment.

Recommendation

Apply workaround: Use the official node:24-bookworm image to avoid potential security risks associated with using NodeSource.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING