Skip to content

GB-138: no core router container was found

Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-138 is printed by goatbuilder. The same text offline: goat explain GB-138 or goatbuilder explain GB-138.

What it means

the selection phase 3 uses (goat federate init) found no running core router on the daemon preflight read: FED_ROUTER_DOCKER_HOST, else the local runtime. Discovery accepts the org.goat.component=zenoh-core label, *-zenoh-router names and legacy goat-zenoh.

Why it happens

  • the core router runs on another host and FED_ROUTER_DOCKER_HOST does not point at it
  • the core router is stopped, or runs under a custom name without the role label

What to do

One line per step or alternative:

export FED_ROUTER_DOCKER_HOST=ssh://<user>@<core> (goatbuilder derives it from the peering's hosts.core, else the one host of inventory group <partner>_core)
export FED_ROUTER_CONTAINER=<name or ID>

Read more

Exit code

goatbuilder exits with 1.