Skip to content

The Goku VM

Royce Davis edited this page Sep 21, 2020 · 1 revision

Initial setup

First run vagrant up goku to bring up the Goku VM. This process will take a while because Vagrant attempts to run through all the provisioning scripts which appear to fail on the first run.

At the moment there is no known method for Ansible to intelligently determine when the VM has successfully rebooted after installing AD so I've inserted a hard-coded wait for 10 minutes. This is painful but the other VMs don't need to go through this.

Ignore any errors and immediately run vagrant provision goku which will take a while but should finish with the following output.

PLAY RECAP *********************************************************************
goku                       : ok=15   changed=12   unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

Accessing via RDP

Pay attention to the port forwarding output when bringing up the Goku VM. In this example the RDP port on 3389 is being forwarded to 2200

==> goku: Forwarding ports...
    goku: 3389 (guest) => 2200 (host) (adapter 1)
    goku: 5985 (guest) => 55985 (host) (adapter 1)
    goku: 5986 (guest) => 55986 (host) (adapter 1)
    goku: 22 (guest) => 2222 (host) (adapter 1)
Clone this wiki locally