-
Notifications
You must be signed in to change notification settings - Fork 177
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Agent Diagnostic
Unable to start OpenShell agent because gateway image cannot be downloaded.
Diagnostics performed:
- Verified Docker daemon is running:
docker psworks correctly - Authenticated to nvcr.io:
docker login nvcr.ioreturned "Login Succeeded" - Attempted to pull gateway image:
docker pull nvcr.io/nvidia/openshell-gateway:latest - Result: "Error response from daemon: error from registry: Access Denied"
The gateway container never started, preventing any agent diagnostics.
This appears to be a registry access permission issue for external Alpha testers.
Description
I am trying to test NemoClaw Alpha on my local workstation. I have completed all environment setup (WSL2, Docker, OpenShell CLI), but I cannot download the required openshell-gateway image from nvcr.io due to "Access Denied" error even after successful login.
The openshell-gateway image should be pulled successfully and the gateway container should start.
Docker returns "Error response from daemon: error from registry: Access Denied"
Reproduction Steps
- Install OpenShell CLI 0.0.10 via GitHub release
- Login to nvcr.io:
docker login nvcr.io(successful) - Run
openshell gateway startor manually pull:docker pull nvcr.io/nvidia/openshell-gateway:latest - Observe "Access Denied" error from registry
Environment
- OS: Windows 11 + WSL2 (Ubuntu 24.04)
- GPU: NVIDIA RTX 5080 (16GB VRAM)
- Docker: Docker Desktop for Windows (WSL2 backend)
- OpenShell CLI: 0.0.10
- NemoClaw: Cloned from GitHub, npm install completed
- nvcr.io: Login successful but image pull denied
Logs
## Logs
$ docker pull nvcr.io/nvidia/openshell-gateway:latest
Error response from daemon: error from registry: Access Denied
Note: I could not complete the Agent-First Checklist items 1 and 2 because
the openshell-gateway image cannot be downloaded, preventing the agent from starting.
The diagnostic above explains the root cause (nvcr.io Access Denied).Agent-First Checklist
- I pointed my agent at the repo and had it investigate this issue
- I loaded relevant skills (e.g.,
debug-openshell-cluster,debug-inference,openshell-cli) - My agent could not resolve this — the diagnostic above explains why
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working