Skip to content

When onboarding to ollama, verifying the proxy fails because nc isn't installed. #4974

@thommay

Description

@thommay

Description

  Configuring Ollama systemd loopback override...
  Applying an Ollama systemd override (OLLAMA_HOST=127.0.0.1:11434). The next steps use sudo to write the drop-in, reload systemd, and restart the service; you may be prompted for your password.
  Error: Ollama auth proxy did not become ready on :11435 within timeout.

function startOllamaAuthProxy(): boolean {
uses waitForPort from
export function waitForPort(port: number, timeoutSeconds = 5): boolean {
which calls nc without verifying that it's available. nc isn't installed on my machine:

> which nc
which: no nc in (/home/thom/.local/bin:/opt/cuda/bin:/home/thom/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/lib/rustup/bin)

Installing nc causes onboarding to proceed.

Reproduction Steps

  1. Run nemoclaw onboard
  2. Select ollama

Environment

+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 610.43.02              KMD Version: 610.43.02     CUDA UMD Version: 13.3     |
+-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 5070 Ti     Off |   00000000:01:00.0  On |                  N/A |
|  0%   42C    P5             29W /  300W |   15621MiB /  16303MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
  • NodeJS v26.1.0
  • Docker version 29.5.2, build 79eb04c7d8

Debug Output

Logs

Checklist

  • I confirmed this bug is reproducible
  • I searched existing issues and this is not a duplicate

Metadata

Metadata

Assignees

Labels

needs: triageAwaiting maintainer classification

Type

No fields configured for Bug.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions