fix: use nvcr.io/nim/nvidia/nemotron-3-nano for NIM local pull (Fixes #66)

[deepujain]

Summary

Fixes #66. Local NIM onboarding was failing when selecting the Nemotron 3 Nano 30B model because docker pull nvcr.io/nim/nvidia/nemotron-3-nano-30b-a3b:latest returns Access Denied from nvcr.io. The image that is actually published and pullable is nvcr.io/nim/nvidia/nemotron-3-nano:latest.

Changes

• bin/lib/nim-images.json: Map model nvidia/nemotron-3-nano-30b-a3b to image nvcr.io/nim/nvidia/nemotron-3-nano:latest instead of nvcr.io/nim/nvidia/nemotron-3-nano-30b-a3b:latest.
• test/nim.test.js: Update the getImageForModel expectation to the new image.

The model identifier (nvidia/nemotron-3-nano-30b-a3b) is unchanged so API/config compatibility is preserved; only the Docker image used for the local NIM container is corrected.

Testing

• npm test (including getImageForModel and nim suite) passes.

Signed-off-by: Deepak Jain deepujain@gmail.com

Summary by CodeRabbit

• Chores

  • Updated the container image reference for the Nemotron 3 Nano model to a different image tag.

• Tests

  • Adjusted unit test expectations to match the new image reference for the Nemotron 3 Nano model.

[wscurran]

Thanks for updating the image tag and ensuring that it uses the correct one, this should resolve any issues with pulling the image.

[cv]

Hey @deepujain! Thanks for putting this together — fixing the NIM local pull image reference is a useful fix. Since this was opened, we've been moving pretty fast on the repo: new CI checks, a bunch of new features, and some structural changes. Would you mind rebasing onto the latest main when you get a chance? That way we can give it a fresh review with everything up to date. Appreciate the contribution!

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 62e2446a-fe89-48b6-ba4a-a1a3b838a1f2

📥 Commits

Reviewing files that changed from the base of the PR and between 14abd40 and 193ede3.

📒 Files selected for processing (2)

• bin/lib/nim-images.json
• test/nim.test.js

✅ Files skipped from review due to trivial changes (2)

• test/nim.test.js
• bin/lib/nim-images.json

---

📝 Walkthrough

Walkthrough

Updated the Docker image reference for the nvidia/nemotron-3-nano-30b-a3b model from nvcr.io/nim/nvidia/nemotron-3-nano-30b-a3b:latest to nvcr.io/nim/nvidia/nemotron-3-nano:latest and adjusted the corresponding unit test expectation.

Changes

Cohort / File(s)	Summary
NIM image mapping & test bin/lib/nim-images.json, test/nim.test.js	Replaced the inaccessible full image name nvcr.io/nim/nvidia/nemotron-3-nano-30b-a3b:latest with the reachable nvcr.io/nim/nvidia/nemotron-3-nano:latest and updated the unit test expectation accordingly.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰
A rabbit hopped by with a fix so neat,
Swapped a long image name for one more sweet.
No more denied pulls, the path is clear,
Local NIM starts with a joyful cheer! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: updating the NIM image reference from nemotron-3-nano-30b-a3b to nemotron-3-nano, which directly addresses the linked issue #66.
Linked Issues check	✅ Passed	The PR successfully resolves issue #66 by updating the image mapping in bin/lib/nim-images.json and corresponding test expectation, addressing the Access Denied error for the nemotron-3-nano-30b-a3b model.
Out of Scope Changes check	✅ Passed	All changes are directly scoped to fixing issue #66: the image mapping update and test expectation adjustment, with no extraneous modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[deepujain]

Rebased on latest main, no conflicts. Tests pass. Thanks for the nudge @cv

[deepujain]

Rebased on latest main, resolved test conflict (upstream vitest migration + image fix). All NIM tests pass. Ready to merge!