Description
In NEMOCLAW_NON_INTERACTIVE=1 mode, when the user is not yet in the docker group, the installer adds the user to the group, then prints manual re-run instructions and exits with code 0 instead of self-completing the flow (group activation → onboard) in a single invocation. After manually running newgrp docker and re-running the install command, onboard completed normally. This breaks the design intent of non-interactive mode and makes CI/CD pipelines unable to detect the failure via exit code.
Environment
| Field |
Value |
| Device |
a1u2n2g-0087-02 |
| OS |
Ubuntu 24.04 |
| Architecture |
x86_64 |
| Node.js |
v22.22.3 |
| npm |
10.9.8 |
| Docker |
29.5.3, build d1c06ef |
| OpenShell CLI |
0.0.44 |
| NemoClaw |
v0.0.55 |
| OpenClaw |
v2026.5.22 |
Steps to Reproduce
Precondition: Docker is NOT installed and the user is NOT in the docker group.
export NEMOCLAW_NON_INTERACTIVE=1
export NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE=1
export NVIDIA_API_KEY=nvapi-xxxxx
curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
Expected Result
A single invocation completes the entire flow: Docker install → docker group activation (e.g. via exec sg docker) → onboard, with no manual intervention required. On any incomplete stage, the installer should exit with a non-zero code.
Actual Result
After adding the user to the docker group, the installer printed manual re-run instructions and exited without completing onboard. Three issues observed:
- [High] Non-interactive mode does not re-enter the shell automatically — after adding the user to the docker group, the installer did not run
exec sg docker to activate the group; instead it exited and required manual action, violating the intent of non-interactive mode.
- [High] Incorrect exit code — the install did not complete the onboard stage but returned
exit 0, so CI/CD pipelines cannot detect the failure via exit code.
- [Medium] Interactive prompts printed in non-interactive mode — under
NEMOCLAW_NON_INTERACTIVE=1 the installer still printed prompts requiring manual action (Run: newgrp docker, Re-run: curl ...).
After manually running newgrp docker and re-running the install command, onboard completed normally.
Logs
[INFO] Docker group membership is not active in this shell yet. To finish:
[INFO] 1) Run: newgrp docker (or log out and log back in)
[INFO] 2) Re-run: curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
Description
In
NEMOCLAW_NON_INTERACTIVE=1mode, when the user is not yet in the docker group, the installer adds the user to the group, then prints manual re-run instructions and exits with code 0 instead of self-completing the flow (group activation → onboard) in a single invocation. After manually runningnewgrp dockerand re-running the install command, onboard completed normally. This breaks the design intent of non-interactive mode and makes CI/CD pipelines unable to detect the failure via exit code.Environment
Steps to Reproduce
Precondition: Docker is NOT installed and the user is NOT in the docker group.
Expected Result
A single invocation completes the entire flow: Docker install → docker group activation (e.g. via
exec sg docker) → onboard, with no manual intervention required. On any incomplete stage, the installer should exit with a non-zero code.Actual Result
After adding the user to the docker group, the installer printed manual re-run instructions and exited without completing onboard. Three issues observed:
exec sg dockerto activate the group; instead it exited and required manual action, violating the intent of non-interactive mode.exit 0, so CI/CD pipelines cannot detect the failure via exit code.NEMOCLAW_NON_INTERACTIVE=1the installer still printed prompts requiring manual action (Run: newgrp docker,Re-run: curl ...).After manually running
newgrp dockerand re-running the install command, onboard completed normally.Logs