> For the complete documentation index, see [llms.txt](https://docs.voting.works/vxsuite-tdp-v4/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voting.works/vxsuite-tdp-v4/software-installation/trusted-build/offline-phase.md).

# Offline Phase

1. To create the **offline** VM with networking disabled, run the following command on the build machine:

```
cd ~/code/vxsuite-build-system
./scripts/tb-create-offline-vm.sh
```

2. Open virt-manager if not already open:

```
sudo virt-manager
```

3. Double click the **offline** VM.
4. Press the start button ▶️.
5. Once the VM has initialized, log in with username **vx** and password **votingworks**.
6. To ensure that the console displays correctly, select "View" > "Resize to VM".
7. In the VM terminal window, validate that networking is automatically disabled in the offline VM using the following command:

```
ping -c2 google.com
```

* This command should either time out or immediately error with a failure in name resolution.

8. To execute the offline phase, run the following commands:

```
cd ~/code/vxsuite-build-system
./scripts/tb-run-offline-phase.sh <inventory-name>
```

9. Once the offline phase completes, the base VotingWorks application has been built. You can now shut down the offline VM:

```
sudo shutdown -h now
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.voting.works/vxsuite-tdp-v4/software-installation/trusted-build/offline-phase.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
