Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[DevOps]: create a Docker image version on NemoClaw per version of OpenClaw

Offen
#62 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Ruhig
Tech-Stack
docker, github-actions
Bereich
ci-cd, devops

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

@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"
]

Vorherrschende Sprache
Dockerfile
Sterne
191
Forks
76
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus NVIDIA/OpenShell-Community

Alle Issues in NVIDIA/OpenShell-Community

Ähnliche Issues

Weitere Issues zu DevOps

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.