Skip to main content
Version: v5.6.1

opschain admin runner show

Included from Basic tier

opschain admin runner show <runner-id>

Shows one runner in full (the v2 RunnerService.GetRunner RPC): identity, lifecycle, drain state, held jobs and the host inventory the runner reported at registration. The default output is a two-column FIELD/VALUE table; -o json|yaml prints the raw document.

The fields, in order: ID, NAME, GROUP, STATE, ONLINE, LAST SEEN, STOPPED, REGISTERED, DRAIN REQUESTED, GROUP DRAINING, LABELS, EXECUTORS, OS/ARCH, GROUP ATTRIBUTES, GROUP BINDINGS, GROUP EXCLUSIVE, JOBS, HOSTNAME, ADDRESSES (IP with MAC where known), CPUS, GO, RUNNER VERSION (with commit), PID, STARTED, STATE DIR, OBSERVED REMOTE (the address the server saw the runner connect from), KEY FINGERPRINT (the registered public key's fingerprint). Empty values render -; timestamps are RFC 3339 UTC.

The GROUP ATTRIBUTES / GROUP BINDINGS / GROUP EXCLUSIVE fields are the runner's group's placement contract, repeated here so a placement question is answerable from one screen — they are edited on the group (opschain docs cli/admin-runner-group-set), not on the runner.

Flags​

FlagMeaning
--server <url>Server base URL. Default: the active context / OPSCHAIN_SERVER.
--auth-token <token>Admin bearer token override. Default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN, then the token stored by opschain admin login.

Exit codes​

0 shown; 1 the request failed (unknown runner id, network, rejected token); 2 usage.

Named errors​

  • a server is required — pass --server <url>, set OPSCHAIN_SERVER, or 'opschain context use <name>' (exit 2)
  • this command needs a login or an admin token — run 'opschain login', pass --auth-token, set OPSCHAIN_ADMIN_TOKEN, or store one with 'opschain admin login' (exit 2)
  • the server rejected the credential — run 'opschain login' again, or check the admin token (exit 1)
  • An unknown id reports the server's refusal as the server answered not_found: … (exit 1).

See also​

  • opschain docs cli/admin-runners-list — the fleet-wide view these ids come from.
  • opschain docs cli/admin-runner-drain / opschain docs cli/admin-runner-forget — the lifecycle verbs on the same id.
  • opschain docs fleet-queue — what the placement fields mean for dispatch.