Skip to content

GB-100: the federation verbs cannot find this party's context directory

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

What it means

goatbuilder federate init (and verify or apply without --as) reads this party's declaration, federation.toml, and init also reads the mTLS certificate and CA roots beside it. goatbuilder has no profile of its own, so it takes the directory from --context-dir, else $GOAT_CONTEXT_DIR, else the goat profile ($GOAT_PROFILE_DIR, else ~/.goat), and none of those was set.

Why it happens

  • none of --context-dir, GOAT_CONTEXT_DIR, GOAT_PROFILE_DIR or HOME is set, as in a bare container or a service unit

What to do

One line per step or alternative:

goatbuilder federate init --context-dir <dir> (the directory holding federation.toml, mtls.cert.pem and ca-roots.pem)
export GOAT_PROFILE_DIR=<goat profile directory> (the verbs then read its active context, as goat does)
goatbuilder federate verify <agreement> --as <sovereign_id> (verify and apply need no context when --as is given)

Read more

Exit code

goatbuilder exits with 2.