[DevOps]: create a Docker image version on NemoClaw per version of OpenClaw
まだ誰も着手していません。
評価
- 難易度
- 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
- PR マージ指標
- 30日以内にマージされた PR はありません
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
NVIDIA/OpenShell-Community のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
-
opencode sandbox policy: npm child-process CONNECT denied (ECONNRESET) and no Vertex AI / WIF egress オープン
難易度 3/5 1〜2日 初心者へのやさしさ 74/100
-
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
-
難易度 4/5 3〜5日 初心者へのやさしさ 45/100
NVIDIA/OpenShell-Community の issue をすべて見る
似ている issue
-
task
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
vsanthanam/JBird#429 ·
-
enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
alexgorbatchev/simple-ptt#14 ·
-
github-request
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
openedx/axim-engineering#1758 · コメント 2 件 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
components-web-app/docs#92 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100