Automatic full disk encryption for OVH Cloud VPS
The supported-image table below is for one path: assisted setup on fresh, unencrypted OVH Cloud VPS images. It is not the full Panocrypt-managed unlock compatibility boundary.
If a Linux system already uses LUKS, or you set up LUKS yourself on another
provider or distro, you can usually bind an unused keyslot to Panocrypt with
your distro’s cryptsetup, Clevis, and the standard Clevis tang pin. No
Panocrypt host software is required for that path. Start with
Bind an existing LUKS volume or
Bind an existing encrypted root disk.
Use this page when you want the Panocrypt setup helper to run after a clean VPS rebuild, set up LUKS on the root disk, bind managed boot unlock, and verify encrypted boot.
Supported OVH Cloud VPS images
Section titled “Supported OVH Cloud VPS images”| Distribution | Versions |
|---|---|
| Ubuntu | 22.04, 24.04, 26.04 |
| Debian | 12, 13 |
| Fedora | 43, 44 |
| Rocky Linux | 9.7, 10.1 |
| AlmaLinux | 10.1 |
| CloudLinux | 9.7 |
Setup command note
Section titled “Setup command note”OVH VPS does not currently provide the same user-data setup path as Hetzner, DigitalOcean, and OCI. For OVH, use the setup command after a clean VPS rebuild.
That distinction matters only for the setup helper. Once the device is bound, managed unlock still runs through LUKS, Clevis, distro initramfs hooks, and Panocrypt policy.
Related guides
Section titled “Related guides”| Goal | Guide |
|---|---|
| Understand the two Panocrypt paths | What runs on your server |
| Understand assisted setup | Assisted fresh-server setup |
| Preserve recovery material | Assisted setup recovery material |
| Compare provider setup paths | Assisted setup providers |
| Learn how LUKS keyslots make removal simple | LUKS keyslots |