Description
After the v0.0.44 release, onboarding can fail during the Docker image build when generate-openclaw-config.py tries to read the OpenClaw model-specific setup manifest for Kimi K2.6 managed inference.
The failing path is:
/opt/nemoclaw-blueprint/model-specific-setup/openclaw/kimi-k2.6-managed-inference.json
The build should not depend on host checkout/source file modes for blueprint manifests. Expected behavior: onboarding should normalize permissions or otherwise ensure model-specific setup manifests are readable inside the build context before running config generation.
Reported from Slack after the v0.0.44 release. At least one user confirmed they are on nemoclaw v0.0.44 and saw the same failure.
Reproduction Steps
- Install or upgrade to NemoClaw v0.0.44.
- Run
nemoclaw onboard or nemoclaw onboard --resume for an OpenClaw setup that includes Kimi K2.6 managed inference.
- Observe the Docker build fail at this step:
Step 55/69 : RUN python3 /usr/local/lib/nemoclaw/generate-openclaw-config.py
Environment
- NemoClaw:
nemoclaw v0.0.44
- Component: onboarding Docker build / OpenClaw config generation
- Full OS, Docker, and Node.js details: not yet captured from reporter
Logs
Step 55/69 : RUN python3 /usr/local/lib/nemoclaw/generate-openclaw-config.py
---> Running in cf67ef6c883d
Traceback (most recent call last):
File "/usr/local/lib/nemoclaw/generate-openclaw-config.py", line 718, in <module>
main()
~~~~^^
File "/usr/local/lib/nemoclaw/generate-openclaw-config.py", line 705, in main
config = build_config()
File "/usr/local/lib/nemoclaw/generate-openclaw-config.py", line 403, in build_config
model_specific_setups = _matching_model_specific_setups(
"openclaw",
...<6 lines>...
env,
)
File "/usr/local/lib/nemoclaw/generate-openclaw-config.py", line 301, in _matching_model_specific_setups
with open(manifest_path, "r", encoding="utf-8") as manifest_file:
~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PermissionError: [Errno 13] Permission denied: '/opt/nemoclaw-blueprint/model-specific-setup/openclaw/kimi-k2.6-managed-inference.json'
Error: × Docker build stream error
╰─▶ Docker stream error: The command '/bin/bash -o pipefail -c python3 /usr/
local/lib/nemoclaw/generate-openclaw-config.py' returned a non-zero
code: 1
Try: openshell sandbox list # check gateway state
Recovery: nemoclaw onboard --resume
Or: nemoclaw onboard
Workaround
This unblocked the reporter:
chmod -R a+rX ~/.nemoclaw/source/nemoclaw-blueprint
docker builder prune -f
nemoclaw onboard --resume
Notes
Existing issue search did not find a duplicate for this specific PermissionError / kimi-k2.6-managed-inference.json failure. This may be related to the broader model-specific setup architecture tracked in #3120, but this issue tracks the release-blocking permission regression and user-facing workaround.
Description
After the v0.0.44 release, onboarding can fail during the Docker image build when
generate-openclaw-config.pytries to read the OpenClaw model-specific setup manifest for Kimi K2.6 managed inference.The failing path is:
The build should not depend on host checkout/source file modes for blueprint manifests. Expected behavior: onboarding should normalize permissions or otherwise ensure model-specific setup manifests are readable inside the build context before running config generation.
Reported from Slack after the v0.0.44 release. At least one user confirmed they are on
nemoclaw v0.0.44and saw the same failure.Reproduction Steps
nemoclaw onboardornemoclaw onboard --resumefor an OpenClaw setup that includes Kimi K2.6 managed inference.Environment
nemoclaw v0.0.44Logs
Workaround
This unblocked the reporter:
chmod -R a+rX ~/.nemoclaw/source/nemoclaw-blueprint docker builder prune -f nemoclaw onboard --resumeNotes
Existing issue search did not find a duplicate for this specific
PermissionError/kimi-k2.6-managed-inference.jsonfailure. This may be related to the broader model-specific setup architecture tracked in #3120, but this issue tracks the release-blocking permission regression and user-facing workaround.