You may run into issues deploying AlienVault OSSIM on top of Proxmox where the fresh install will be unable to scan the network and the local sensor will not be active. This issue is related to dynamic memory allocation in Proxmox. A similar issue is mentioned here for Hyper-V.
Proxmox, like Hyper-V, uses dynamic RAM allocation for containers and VMs by default as described in the official documentation. Although you can set the minimum and maximum to the same value, I found that the ballooning device option must be unchecked for OSSIM to run properly. My memory configuration is shown below.
