`docker_host: automount` is a later act_runner's spelling of the default, and
0.3.1 does not know the word: it exits with `unable to parse docker host
automount` and restart-loops — registered, visible in Gitea, never online, and
the logs say nothing about the config file.
On 0.3.x the empty value is the one that finds a daemon *and* passes it to the
job containers, which is what `docker.yml` needs; `"-"` is the value that
withholds it. Both spellings are now in the guide's failure table, because the
symptom points at the daemon rather than at the one word that caused it.
Verified in the job image on the runner host: Ubuntu 24.04 as root, node 24,
Python 3.12.3, npm, curl and unzip (the SDK script's dependencies), apt-get
update/install, `python3 -m venv` plus pip, `docker version` against the host's
27.5.1 through the mounted socket, and openjdk-21-jdk-headless landing exactly
at the `JAVA_HOME` the Android jobs assume.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
timka123andClaude Opus 5
4584a5324d