Skip to content

Buildkite Test Agent Setup

We are using Buildkite for Windows and macOS testing. The build machines and buildkite-agent must be set up before use.

Windows Test Agent Setup

  1. Create the user “testbot” on the machine. Use the password for, available in 1Password.
  2. In admin PowerShell, wsl --install.
  3. In admin PowerShell, Set-ExecutionPolicy -Scope "CurrentUser" -ExecutionPolicy "RemoteSigned".
  4. In admin PowerShell, download and run windows_buildkite_start.ps1 with curl <url> -O windows_buildkite_start.ps1.
  5. After restart, in administrative Git Bash window, Rename-Computer <testbot-win10(home|pro)-<description>-1 and then export BUILDKITE_AGENT_TOKEN=<token>.
  6. Now download and run
  7. Download and run
  8. Launch Docker. It may require you to take further actions.
  9. Log into Chrome with the user and enable Chrome Remote Desktop.
  10. Enable gd, fileinfo, and curl extensions in /c/tools/php*/php.ini.
  11. If a laptop, set the “lid closing” setting to do nothing.
  12. Set the “Sleep after time” setting in settings to never.
  13. Install winaero tweaker and “Enable user autologin checkbox”. Set up the machine to automatically log in on boot. Then run netplwiz, provide the password for the main user, uncheck “require a password to log in”.
  14. Set the buildkite-agent service to run as the testbot user and use delayed start: Choose “Automatic, delayed start” and on the “Log On” tab in the services widget it must be set up to log in as the testbot user, so it inherits environment variables and home directory (and can access NFS, has testbot Git config, etc).
  15. git config --global --add '*'.
  16. Manually run, curl -sL -O && bash
  17. Run .buildkite/ to check your work.
  18. Reboot the machine and do a test run. (On Windows, the machine name only takes effect on reboot.)
  19. Verify that go, ddev, git-bash are in the path.
  20. In “Advanced Windows Update Settings” enable “Receive updates for other Microsoft products” to make sure you get WSL2 kernel upgrades. Make sure to run Windows Update to get the latest kernel.

Additional Windows Setup for WSL2+Docker Desktop Testing

  1. The Ubuntu distro should be set up with the user buildkite-agent
  2. buildkite-agent should have home directory /var/lib/buildkite-agent: sudo usermod -d /var/lib/buildkite-agent buildkite-agent
  3. Configure buildkite agent in /etc/buildkite-agent:
    • tags=”os=wsl2,architecture=amd64,dockertype=wsl2”
    • token=”xxx”
  4. wsl.exe --update
  5. Open WSL2 and check out ddev/ddev.
  6. Install DDEV using the standard WSL2 Docker Desktop installation.
  7. Delete the CAROOT and WSLENV environment variables from administrative PowerShell:

    [Environment]::SetEnvironmentVariable("CAROOT", $null, "Machine")
    [Environment]::SetEnvironmentVariable("WSLENV", $null, "Machine")
  8. Configure brew in PATH with:

    echo "export PATH=/home/linuxbrew/.linuxbrew/bin:$PATH" >>~/.bashrc
    source ~/.bashrc
  9. As root user, add sudo capability with echo "ALL ALL=NOPASSWD: ALL" >/etc/sudoers.d/all && chmod 440 /etc/sudoers.d/all.

  10. Manually run, .buildkite/
  11. git config --global --add '*'
  12. Install basics in WSL2:

    curl -fsSL | gpg --dearmor | sudo tee /etc/apt/keyrings/ddev.gpg > /dev/null
    echo "deb [signed-by=/etc/apt/keyrings/ddev.gpg] * *" | sudo tee /etc/apt/sources.list.d/ddev.list >/dev/null
    # Update package information and install DDEV
    sudo apt update && sudo apt install -y build-essential ddev icinga2 mariadb-client
    brew install docker-compose golang 
    sudo mkdir -p /usr/sharekeyrings && curl -fsSL | sudo gpg --dearmor -o /usr/share/keyrings/buildkite-agent-archive-keyring.gpg
    echo "deb [signed-by=/usr/share/keyrings/buildkite-agent-archive-keyring.gpg] stable main" | sudo tee /etc/apt/sources.list.d/buildkite-agent.list
    sudo apt update && sudo apt install -y build-essential buildkite-agent ca-certificates curl ddev etckeeper gnupg icinga2 nagios-plugins lsb-release make mariadb-client
    (mkcert -uninstall || true); rm -rf $(mkcert -CAROOT) || true; mkcert -install
    sudo snap install --classic go
    sudo snap install ngrok
    sudo systemctl enable buildkite-agent && sudo systemctl start buildkite-agent
  13. Verify that buildkite-agent is running.

  14. Follow the Icinga instructions to configure the agent. Under the “Agent” tab it provides a script to configure the agent.
  15. Windows Terminal should be installed. Set “Ubuntu” as the default and have it start on Windows startup.
  16. echo "capath=/etc/ssl/certs/" >>~/.curlrc
  17. nc.exe -L -p 9003 on Windows to trigger and allow Windows Defender.
  18. Run ngrok config add-authtoken <token> with token for free account.

Additional Windows Setup for WSL2+Docker-Inside Testing

  1. Uninstall Docker Desktop.
  2. Remove all of the entries (especially host.docker.internal) that Docker Desktop might have added in C:\Windows\system32\drivers\etc\hosts.
  3. Install Docker and basics in WSL2:

    sudo mkdir -p /etc/apt/keyrings
    sudo mkdir -p /etc/apt/keyrings && sudo rm -f /etc/apt/keyrings/docker.gpg && curl -fsSL | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
    echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
    sudo apt update && sudo apt install -y docker-ce docker-ce-cli etckeeper docker-compose-plugin
    sudo usermod -aG docker $USER
  4. Run .buildkite/

Icinga2 monitoring setup for WSL2 instances

  1. Icinga Director web UI, configure the host on, normally making a copy of an existing identical item.
  2. Deploy the new host using Icinga Director.
  3. On the WSL2 Ubuntu instance, install needed packages: sudo apt update && sudo apt install -y etckeeper icinga2 monitoring-plugins-contrib nagios-plugins
  4. Add nagios to the docker group in /etc/group.
  5. sudo icinga2 node wizard to configure the agent, see docs
  6. Restart sudo systemctl restart icinga2
  7. Hope that it can all work sometime.

macOS Docker Desktop Test Agent Setup (Intel and Apple Silicon)

  1. Create the user “testbot” on the machine. Use the password for, available in 1Password.
  2. Change the name of the machine to something in keeping with current style, perhaps testbot-macos-arm64-8. This is done in SettingsGeneralAboutName and in SharingComputer Name and in SharingLocal Hostname.
  3. Download and install Chrome and log the browser into the account used for test runners. It will pick up the Chrome Remote Desktop setup as a result. Configure Chrome Remote Desktop to serve. When this is done, the machine will be available for remote access and most other tasks can be done using Chrome Remote Desktop.
  4. The machine should be on the correct network and have a static IP handed out by DHCP. IP addresses are listed in /etc/hosts on, so this one should be added.
  5. Power should be set up as in macos power settings.
  6. Auto login should be set up as in macos users and groups, see automatically log in on boot.
  7. Remote login should be enabled as in macos remote login.
  8. Automatic updates should be set to mostly security only as in macos automatic_updatees.
  9. Set the time zone to US MT (nearest city: Denver, Colorado).
  10. sudo mkdir -p /usr/local/bin && sudo chown -R testbot /usr/local/bin
  11. Install Homebrew /bin/bash -c "$(curl -fsSL"
  12. After installing Homebrew follow the instructions it gives you at the end to add brew to your PATH.
  13. Install everything you’ll need with brew install buildkite/buildkite/buildkite-agent bats-core composer ddev/ddev/ddev git golang jq mariadb mkcert netcat p7zip && brew install --cask docker iterm2 ngrok.
  14. Run ngrok authtoken <token> with token for free account from 1Password.
  15. Run mkcert -install.
  16. If Docker Desktop will be deployed, run Docker manually and go through its configuration routine.
  17. If OrbStack will be deployed, install it from
    • Install with Docker only.
    • Click “Sign in” in the lower left to sign in with OrbStack credentials (normal test runner gmail address; it will receive an email with a login code).
    • Configure it to automatically start and download updates, see OrbStack configuration.
  18. If Rancher Desktop will be deployed, install it.
    • Turn off kubernetes.
  19. Run iTerm. You may need to allow full disk access permissions.
  20. Run mkdir ~/workspace && cd ~/workspace && git clone
  21. Set up nfsd by running bash ~/workspace/ddev/scripts/
  22. git config --global --add '*'.
  23. Edit /usr/local/etc/buildkite-agent/buildkite-agent.cfg or /opt/homebrew/etc/buildkite-agent/buildkite-agent.cfg to add
    • the agent token (from agents tab, “Reveal Agent Token”).
    • the agent name (the name of the machine).
    • tags, like "os=macos,architecture=arm64,osvariant=sonoma,dockertype=dockerformac,rancher-desktop=true,orbstack=true,docker-desktop=true"
    • build-path="~/tmp/buildkite-agent/builds"
  24. Run brew services start buildkite-agent.
  25. Run bash ~/workspace/ddev/.buildkite/
  26. Run bash ~/workspace/ddev/.buildkite/ to check your work.
  27. The testbot user’s ssh account is used for monitoring, so ssh-keygen and then add the public key id_testbot from 1Password to ~/.ssh/authorized_keys and chmod 600 ~/.ssh/authorized_keys.
  28. Add the new machine to Icinga by copying an existing Icinga service to the new one. This is done in Icinga DirectorServicesSingle ServicesSelect a ServiceCloneDeploy. The new service has to have by-ssh-address set to the name of the test runner, and that address needs to be added to’s /etc/hosts file.
  29. If zsh is the shell configured, add /etc/zshenv so that /usr/local/bin/docker will be picked up:


Additional Colima macOS setup

  1. brew install colima
  2. colima start --cpu 4 --memory 6 --disk 100 --vm-type=qemu --mount-type=sshfs --dns=
  3. colima stop
  4. colima start vz --cpu 4 --memory 6 --disk 60 --vm-type=vz --mount-type=virtiofs --dns=
  5. colima stop vz

Then the Buildkite agent must be configured with tags colima=true and colima_vz=true.

Additional Lima macOS setup (not yet working)

  1. limactl create --name=lima-vz --vm-type=vz --mount-type=virtiofs --mount="~/:w" --memory=6 --cpus=4 --disk=100 template://docker
  2. limactl start lima-vz
  3. docker context use lima-lima-vz

Then the Buildkite agent must be configured with tags lima=true.