Description
When onboarding is blocked by an unsupported DOCKER_HOST value, the CLI shows the advisory title and remediation but omits the advisory identifier. This prevents users and tooling from distinguishing the finding by its stable product identifier.
Platform scope: Reproduced on Ubuntu 24.04 and WSL2; macOS was not tested.
Regression: Unknown — earlier versions not tested.
Environment
Device: Ubuntu test host
OS: Ubuntu 24.04.4 LTS
Architecture: x86_64
Node.js: v22.23.1
npm: 10.9.8
Docker: Docker version 29.5.3, build d1c06ef
OpenShell CLI: openshell 0.0.85
NemoClaw: nemoclaw v0.0.103
OpenClaw: N/A (onboarding blocked during preflight)
Steps to Reproduce
-
On Ubuntu 24.04 with Docker running, unset any explicit Docker context:
-
Set an unsupported Docker endpoint using a documentation-only address:
export DOCKER_HOST=tcp://192.0.2.10:2375
-
Run:
nemoclaw onboard --fresh --name invalid-docker-host-test --non-interactive --yes --yes-i-accept-third-party-software
-
Inspect the preflight advisory written to the terminal.
Expected Result
Onboarding exits nonzero. The advisory output includes the stable identifier invalid_docker_host, actionable commands to unset DOCKER_HOST or select an absolute Unix socket, and does not show docker_group_permission or start_docker findings.
Actual Result
Onboarding exits nonzero and shows the correct title and remediation, but invalid_docker_host is absent:
[1/8] Preflight checks
✗ Docker is not reachable. Please fix Docker and try again.
Suggested fix:
- Fix the DOCKER_HOST endpoint: DOCKER_HOST is set to an endpoint onboarding cannot use.
unset DOCKER_HOST
export DOCKER_HOST=unix:///var/run/docker.sock
Logs
[1/8] Preflight checks
✗ Docker is not reachable. Please fix Docker and try again.
Suggested fix:
- Fix the DOCKER_HOST endpoint: DOCKER_HOST is set to an endpoint onboarding cannot use. Onboarding supports only an absolute unix:// Docker socket. TCP and SSH endpoints and relative paths are not supported, even when reachable.
unset DOCKER_HOST
export DOCKER_HOST=unix:///var/run/docker.sock
Description
When onboarding is blocked by an unsupported
DOCKER_HOSTvalue, the CLI shows the advisory title and remediation but omits the advisory identifier. This prevents users and tooling from distinguishing the finding by its stable product identifier.Platform scope: Reproduced on Ubuntu 24.04 and WSL2; macOS was not tested.
Regression: Unknown — earlier versions not tested.
Environment
Steps to Reproduce
On Ubuntu 24.04 with Docker running, unset any explicit Docker context:
unset DOCKER_CONTEXTSet an unsupported Docker endpoint using a documentation-only address:
export DOCKER_HOST=tcp://192.0.2.10:2375Run:
Inspect the preflight advisory written to the terminal.
Expected Result
Onboarding exits nonzero. The advisory output includes the stable identifier
invalid_docker_host, actionable commands to unsetDOCKER_HOSTor select an absolute Unix socket, and does not showdocker_group_permissionorstart_dockerfindings.Actual Result
Onboarding exits nonzero and shows the correct title and remediation, but
invalid_docker_hostis absent:Logs