Addons guide builder instructions don't work

[davet2001]

Following the page
https://developers.home-assistant.io/docs/add-ons/publishing#custom-add-ons,
when I try to build a local addon using the provided instructions I get the following output:

$ docker run \
  --rm \
  --privileged \
  -v ~/.docker:/root/.docker \
  -v mitmproxy:/data \ 
  homeassistant/amd64-builder \
  --all \
  -t /data
[22:22:24] INFO: Setup crosscompiling feature
[22:22:24] WARNING: Can't enable crosscompiling feature
[22:22:24] INFO: Starting docker.
[22:22:24] INFO: Waiting for docker to initialize...
[22:22:25] INFO: Docker was initialized
[22:22:25] INFO: Run addon build for: armhf armv7 amd64 i386 aarch64
jq: error: Could not open file /tmp/build_config/config.json: No such file or directory
jq: error: Could not open file /tmp/build_config/config.json: No such file or directory
jq: error: Could not open file /tmp/build_config/config.json: No such file or directory
jq: error: Could not open file /tmp/build_config/config.json: No such file or directory
jq: error: Could not open file /tmp/build_config/config.json: No such file or directory

Perhaps I'm missing something, but I thought the addons switched over to using config.yaml and build.yaml instead of their json counterparts about 2 years ago.

Happy to be pointed in the right direction and create a PR for updated documentation but that's what happens when I follow the instructions as they are now.

[wez]

FWIW, I hit the same thing, but it was resolved by changing:
-v mitmproxy:/data
to
-v ./mitmproxy:/data

[kskouzmin]

No i was going through this tutorial https://developers.home-assistant.io/docs/add-ons/testing
with the command:

docker run \
  --rm \
  -it \
  --name builder \
  --privileged \
  -v /path/to/addon:/data \
  -v /var/run/docker.sock:/var/run/docker.sock:ro \
  homeassistant/amd64-builder \
  -t /data \
  --all \
  --test \
  -i my-test-addon-{arch} \
  -d local

...and got a exactly this error messages if a run not in home directory. So it is really could not fing a expected config files!