abiosoft/colima · warning

error setting up network dependencies: %w

Error message

error setting up network dependencies: %w

What it means

Logged as a warning (network failure is explicitly non-fatal for vmnet setup) when the daemon chain a.Exec() failed and the network dependency was never installed (ctx networkInstalledKey != true). It wraps the same chain error and signals that installing the vmnet/network dependencies (root daemon + vmnet networking) failed, so addressable networks will not work for this start.

Source

Thrown at environment/vm/lima/daemon.go:111

			if !s.Running {
				return fmt.Errorf("daemon is not running")
			}
			for _, p := range s.Processes {
				if !p.Running {
					return p.Error
				}
			}
			return nil
		})
	}

	// network failure is not fatal
	if err := a.Exec(); err != nil {
		if useVmnet {
			func() {
				installed, _ := ctx.Value(networkInstalledKey).(bool)
				if !installed {
					log.Warnln(fmt.Errorf("error setting up network dependencies: %w", err))
					return
				}

				status, ok := ctx.Value(statusKey).(daemon.Status)
				if !ok {
					return
				}
				if !status.Running {
					log.Warnln(fmt.Errorf("error starting network: %w", err))
					return
				}

				for _, p := range status.Processes {
					// TODO: handle inotify separate from network
					if p.Name == inotify.Name {
						continue
					}
					if !p.Running {

View on GitHub (pinned to c3a5f9184d)

Solutions

1. Ensure vmnet helpers exist and run: on brew installs 'brew install socket_vmnet' (colima bundles sudoers setup) and verify passwordless sudo for the helper per colima docs.
2. Retry with defaults first ('colima start') to confirm the VM itself is fine, then add --network-address back.
3. Run colima with verbose logging (COLIMA_LOG_LEVEL/debug or 'colima start -v') to surface the underlying install error from the wrapped err.
4. If sudo is the blocker, run once from an interactive sudo-capable shell so the installer can set up the vmnet daemon.
5. Recreate the VM if partial network state lingers: 'colima delete -f && colima start --network-address'.

// verify vmnet helper availability before enabling addressable networks
if conf.Network.Address {
    if _, err := exec.LookPath("vde_vmnet"); err != nil {
        if _, err := exec.LookPath("socket_vmnet"); err != nil {
            return fmt.Errorf("vmnet helpers not installed; brew install socket_vmnet")
        }
    }
}

// daemon.go already degrades to a warning; mirror that in callers
if err := a.Exec(); err != nil {
    if !installed {
        log.Warnln(fmt.Errorf("error setting up network dependencies: %w", err)) // continue start
    }
}

When it happens

Trigger: 'colima start --network-address' (or networks: in config) where deps.Install for the network/vmnet daemon failed: sudo prompt/permission failure on the host for vde_vmnet/socket_vmnet, missing vmnet helpers, macOS refusing VM network entitlements, or the guest-side install failing; because installation never completed, the installed flag stays false and this branch warns instead of the more specific 'error starting network'.

Common situations: First use of --network-address on machines where socket_vmnet/vde_vmnet is absent or not sudo-runnable; colima installed via brew without the vmnet helpers; corporate sudo policies blocking the non-interactive install; macOS updates breaking vmnet entitlements.

Related errors

• error starting network: %w
• error starting %s: %w
• cannot make dir: %w
• error reading pid file: %w
• error preparing vmnet: %w

AI-assisted analysis of abiosoft/colima@c3a5f9184d (2026-08-15). Data as JSON: /api/errors/77ebd39d7218e427. Report an issue: GitHub.