[DevOps]: create a Docker image version on NemoClaw per version of OpenClaw
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
调研方向
Review PR #55 and the current NemoClaw image build first; use npm view openclaw versions --json to understand the version source. Define the recurring repository workflow so each available OpenClaw version produces a NemoClaw image with an OpenClaw-version tag, and verify the optional dual-tag behavior if adopted.
由索引模型根据 Issue 内容生成。
描述
@johntmyers : this is a continuation of https://github.com/NVIDIA/OpenShell-Community/pull/55 based on your remrark.
Currently, NemoClaw image defines and uses 1 single OpenClaw version in its buzild. Frequent updates would be needed to keep it up to date as OpenClaw evolves very fast.
A much better approach is to build one version of the NemoClaw image for OpenClaw for each OpenClaw version. The list of available OpenClaw packages is easy to obtain via the command below
So, it would be good to let the user choose the version of OpenClaw that he wants by having 1 image available for each of those versions.
Consequently, there should be a workflow in this repo running regurlary and creating new versions of NemoClaw when new versions of OpenClaw get publshed. Those images would be tagged ith the version of OpenClaw.
Optionally, those images could have a dual tag + as NemoClaw also gets updated to offer choices in the 2 dimensions
npm view openclaw versions --json
[
"0.0.1",
"2026.1.29-beta.1",
"2026.1.29-beta.2",
"2026.1.29-beta.3",
"2026.1.29-beta.4",
"2026.1.29-beta.5",
"2026.1.29-beta.7",
"2026.1.29",
"2026.1.30",
"2026.2.1",
"2026.2.2-1",
"2026.2.2-2",
"2026.2.2-3",
"2026.2.2",
"2026.2.3-1",
"2026.2.3",
"2026.2.6-1",
"2026.2.6-2",
"2026.2.6-3",
"2026.2.6",
"2026.2.9",
"2026.2.12",
"2026.2.13",
"2026.2.14",
"2026.2.15",
"2026.2.17",
"2026.2.19-1",
"2026.2.19-2",
"2026.2.19",
"2026.2.21-1",
"2026.2.21-2",
"2026.2.21",
"2026.2.22-1",
"2026.2.22-2",
"2026.2.22",
"2026.2.23-beta.1",
"2026.2.23",
"2026.2.24",
"2026.2.25-beta.1",
"2026.2.25",
"2026.2.26",
"2026.3.1-beta.1",
"2026.3.1",
"2026.3.2-beta.1",
"2026.3.2",
"2026.3.7-beta.1",
"2026.3.7",
"2026.3.8-beta.1",
"2026.3.8",
"2026.3.11-beta.1",
"2026.3.11",
"2026.3.12",
"2026.3.13-beta.1",
"2026.3.13",
"2026.3.22-beta.1",
"2026.3.22",
"2026.3.23-1",
"2026.3.23-2",
"2026.3.23-beta.1",
"2026.3.23",
"2026.3.24-beta.1",
"2026.3.24-beta.2",
"2026.3.24",
"2026.3.28-beta.1",
"2026.3.28",
"2026.3.31-beta.1",
"2026.3.31",
"2026.4.1-beta.1",
"2026.4.1",
"2026.4.2"
]
- 主要语言
- Dockerfile
- 星标
- 191
- 派生
- 76
- 平均合并
- 2 小时 59 分钟
- 30 天内合并 PR
- 1
环境准备
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
jose-compu/smart-contract-verification#26 ·
维护者通常 3 天内回复
-
self-driving
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
area-action bug follow-up priority-high
难度 2/5 1-3 小时 新手友好度 88/100
yschimke/design-parity#495 ·
维护者通常 1 天内回复
-
follow-up
难度 2/5 1-3 小时 新手友好度 88/100
yschimke/homeassistant-remotecompose#680 ·
维护者通常 1 天内回复