Skip to content

GB-300: the phone's Linux VM is not a host a node can be built on

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

What it means

For a phone node, phase 2 of join-node prepares the phone's Linux VM (Debian's kernel with its boot settings, Docker Engine, the deploy user) and then runs the integrity checks in the VM (ops/scripts/phone-node-provision.sh, ops/scripts/phone-node-integrity.sh). The VM could not be prepared, did not come back on Debian's kernel, or failed a check; the line before this one names which. No later phase ran, so nothing is built on the VM.

Why it happens

  • the VM started again on the kernel Android supplies, or without the boot settings
  • file reads differ between cache drops, a write does not read back the same, or an installed file fails dpkg --verify: the VM returns wrong file data
  • the kernel log holds a filesystem or I/O error
  • the WireGuard module does not load, or a container does not run
  • the phone does not support a VM, or has no Linux Terminal app

What to do

One line per step or alternative:

read the `integrity:` line the phase printed; it names the check
ops/scripts/phone-node-provision.sh --node <node> --check (the checks alone)
a VM that returns wrong file data is reset and prepared again: ops/scripts/phone-node-provision.sh --node <node> --reset
then resume: goatbuilder join-node <environment> --site <site> --node <node> --class phone --via usb --from 2

Read more

Exit code

goatbuilder exits with 1.