> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/1.2/getting-started/generate-linux-boot-images.md).

# Generate Linux boot images

Linux boot images are generated using a similar process as Windows PE boot images.  Select the appropriate boot image in the boot images list and choose either **Generate** or **Regenerate** to update the boot image.  (Note that with Linux boot images there is no difference between these two actions; both completely regenerate the Linux boot image each time they are executed.)

While there are the same content items available in the Linux boot image properties, only one is presently used:

* **Certificates**.  One or more root certificates (typically from an internal PKI) can be placed in a folder and uploaded to DeployR as a content item with an **Other** purpose. Select this content item, and **Generate** the boot image to add those files.

{% hint style="info" %}
Note: The Linux boot image generation process requires installing the Windows Subsystem for Linux (WSL), which requires hardware-assisted virtualization (for physical machines) or nested virtualization support (for virtual machines).  This will be automatically configured when needed.

Due to limitations in WSL that prevent access from a "Local System" account, the DeployR service will leverage a scheduled task running as the server's logged on user to complete the Linux boot image generation process.

Also, it is not presently possible to generate an ARM64 Linux boot image from from an x64 Windows environment.
{% endhint %}


---

# 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://documentation.2pintsoftware.com/deployr/1.2/getting-started/generate-linux-boot-images.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.