Embed get_buildroot_testvector.py to get_images.sh and it is only used when specifying building.

docs/docker/README.md

@@ -30,9 +30,7 @@ If you have any other questions, please read the [troubleshooting]() first.
 Steps:
 
 1. Install either Docker Engine or Podman for container support
-2. (If you want to build image your own) Run `get_buildroot_testvector.py` to get the buildroot and testvector configuration from relative path.
-    - `python get_buildroot_testvector.py` is the command to run.
-3. Run start-up script `docs/docker/start.sh` to start a stateless container to run the toolchains and EDA tool
+2. Run start-up script `docs/docker/start.sh` to start a stateless container to run the toolchains and EDA tool
 
 ### Docker Engine or Podman
 
@@ -171,10 +169,10 @@ Because we are going to use the whole environment of ubuntu to get both executab
 
 There are four scripts:
 
-- `get_buildroot_testvector.py`: copy buildroot and testvector configuration required by building
 - `start.sh` (most often used): start running the container
     - if you don't care about toolchains and running regression automatically, this script is only thing you need to know
 - `get_images.sh`: get docker image `wallysoc/ubuntu_wally` or `wallysoc/toolchains_wally`
+- `get_buildroot_testvector.py`: copy buildroot and testvector configuration required by building
 - `run_regression.sh`: run regressions with Verilator (and QuestaSIM) on specific CVW
     - this script is not intended to be run directly, but inside the container
     - However, it is a good resource to look into to know what is happening

docs/docker/get_images.sh

@@ -15,6 +15,7 @@ else
 fi
 
 if [ $TOOLCHAINS_BUILD -eq 1 ]; then
+    `which python` get_buildroot_testvector.py
     ${DOCKER_EXEC} build -t toolchains_wally -f Dockerfile.builds .
     ${DOCKER_EXEC} tag toolchains_wally:latest wallysoc/toolchains_wally:latest
 else