> 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/reference/step-definitions/add-luks-passphrase.md).

# Add LUKS passphrase

{% hint style="info" %}
This is only supported in DeployR Enterprise. Applies to: DeployR 1.2 and later.
{% endhint %}

When installing Ubuntu with LVM and LUKS encryption enabled, a passphrase is used to unlock the volume during the boot process. The **Add LUKS passphrase** step lets you add another passphrase while retaining the original one.

<figure><img src="https://content.gitbook.com/content/8m0VARX9oyZ2zXWCdPgr/blobs/bpxhHcnc4qrtV0cIeTKw/image.png" alt=""><figcaption></figcaption></figure>

The original LUKS passphrase is needed to add the new passphrase.

### Options

| Option                                     | Description                                                   |
| ------------------------------------------ | ------------------------------------------------------------- |
| LUKS disk encryption passphrase (existing) | The current passphrase that unlocks the disk.                 |
| LUKS disk encryption passphrase (new)      | The passphrase to add. The existing passphrase keeps working. |


---

# 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/reference/step-definitions/add-luks-passphrase.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.
