Commit 76ec2a16 authored by kwadronaut's avatar kwadronaut

add info about proxmox failing #8683

parent 7a542ec2
......@@ -105,3 +105,5 @@ Special Environments
When deploying to OpenStack release "nova" or newer, you will need to do an initial deploy, then when it has finished run `leap facts update` and then deploy again (see: https://leap.se/code/issues/3020)
It is not possible to actually use the EIP openvpn server on vagrant nodes (see: https://leap.se/code/issues/2401)
Proxmox virtualization isn't supported because it wants to overwrite our resolv.conf (see: https://leap.se/code/issues/8683)
......@@ -22,7 +22,7 @@ NOTE: You won't be able to run that `leap list` command yet, not until we actual
1. A workstation: This is your local machine that you will run commands on.
1. A server: This is the machine that you will deploy to. The server can be either:
1. A local Vagrant virtual machine: a Vagrant machine can only be useful for testing.
1. A real or paravirtualized server: The server must have Debian Jessie installed, and you must be able to SSH into the machine as root. Paravirtualization includes KVM, Xen, OpenStack, Amazon, but not VirtualBox or OpenVZ.
1. A real or paravirtualized server: The server must have Debian Jessie installed, and you must be able to SSH into the machine as root. Paravirtualization includes KVM, Xen, OpenStack, Amazon, but not VirtualBox or OpenVZ. Proxmox has an known issue when changing the resolver: https://leap.se/code/issues/8683
Other things to keep in mind:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment