Description
Description
NemoClaw v0.0.43 onboard fails at step [6/8] "Creating sandbox" on Brev
when the sandbox base image needs local rebuild (published base has glibc
2.36, OpenShell supervisor requires >= 2.39). Dockerfile.base Step 11 uses
RUN --mount=type=bind which requires BuildKit, but the host Docker uses
the legacy builder. The build aborts with:
"the --mount option requires BuildKit"
The NemoClaw build command does not set DOCKER_BUILDKIT=1 as a fallback,
so any host without BuildKit enabled by default will fail.
Workaround: sudo mkdir -p /etc/docker && echo '{"features":{"buildkit":true}}'
| sudo tee /etc/docker/daemon.json && sudo systemctl restart docker
Fix: set DOCKER_BUILDKIT=1 in the environment before invoking docker build
in the sandbox base image build path.
Environment
Device: Brev instance (nemoclaw-4e69a8-inst-...)
OS: Ubuntu 22.04 LTS
Architecture: x86_64
Node.js: v22.22.3
npm: 10.9.8
Docker: Docker 29.2.1 (legacy builder, no BuildKit)
OpenShell CLI: openshell 0.0.39
NemoClaw: v0.0.43
OpenClaw: N/A (onboard failed)
Steps to Reproduce
1. Brev Ubuntu 22.04 instance, Docker 29.2.1, no /etc/docker/daemon.json
2. Install NemoClaw from main branch (v0.0.43)
3. Run: nemoclaw onboard (select NVIDIA Endpoints, any model)
4. At step [6/8], sandbox base image glibc check triggers local rebuild
5. Docker build fails at Step 11/11 with --mount error
Expected Result
Sandbox base image builds successfully regardless of whether the host
Docker has BuildKit enabled by default. The build command should set
DOCKER_BUILDKIT=1 explicitly, or the Dockerfile should avoid BuildKit-
only syntax (--mount) for compatibility with legacy builders.
Actual Result
Step 11/11 : RUN --mount=type=bind,source=nemoclaw-blueprint/blueprint.yaml,...
the --mount option requires BuildKit. Refer to https://docs.docker.com/go/buildkit/
Command failed (exit 1): docker build -f ~/.nemoclaw/source/Dockerfile.base ...
Onboard aborts. No sandbox created. User left with no workaround guidance.
Logs
DEPRECATED: The legacy builder is deprecated and will be removed in a
future release. Install the buildx component to build images with BuildKit.
Sending build context to Docker daemon 232.3MB
Step 1/11 through Step 10/11: all pass (Using cache)
Step 11/11 : RUN --mount=type=bind,...
the --mount option requires BuildKit.
Bug Details
| Field |
Value |
| Priority |
Unprioritized |
| Action |
Dev - Open - To fix |
| Disposition |
Open issue |
| Module |
Machine Learning - NemoClaw |
| Keyword |
NemoClaw, NEMOCLAW_GH_SYNC_APPROVAL, NemoClaw_Onboard, NemoClaw_Sandbox, NemoClaw-SWQA-RelBlckr-Recommended |
[NVB#6180350]
Description
Description
NemoClaw v0.0.43 onboard fails at step [6/8] "Creating sandbox" on Brev when the sandbox base image needs local rebuild (published base has glibc 2.36, OpenShell supervisor requires >= 2.39). Dockerfile.base Step 11 uses RUN --mount=type=bind which requires BuildKit, but the host Docker uses the legacy builder. The build aborts with: "the --mount option requires BuildKit" The NemoClaw build command does not set DOCKER_BUILDKIT=1 as a fallback, so any host without BuildKit enabled by default will fail. Workaround: sudo mkdir -p /etc/docker && echo '{"features":{"buildkit":true}}' | sudo tee /etc/docker/daemon.json && sudo systemctl restart docker Fix: set DOCKER_BUILDKIT=1 in the environment before invoking docker build in the sandbox base image build path.Environment Steps to Reproduce Expected Result Actual Result LogsBug Details
[NVB#6180350]