Pulse LXC configuration impacts snapshots and container migration #738
Description
Hi,
First of all let me thank you for this wonderful project. It's being a little bit confusing setting it up correctly, took way longer than I hoped/expected, but I'm almost done. It's great to be able to monitor all proxmox LXC/VMs and all docker containers in one simple dashboard.
While setting up everything I noticed a problem: the Pulse LXC is being created with a bind mountpoint. In pulse lxc .conf file you can see:
mp0: /run/pulse-sensor-proxy,mp=/mnt/pulse-proxy,replicate=0
When migrating the LXC to another node, it fails, because of that mountpoint (it can't snapshot and replicate it to the other node). It's a known issue with Proxmox, but luckily there's a valid workaround (described in this post).
The workaround is configuring the bind mountpoint using LXC configuration directives so Proxmox will allow snapshots and consequently the migration won't fail. So the above line has to be replaced with the following:
lxc.mount.entry: /run/pulse-sensor-proxy mnt/pulse-proxy none bind 0 0
It will have the same effect, but it won't trigger Proxmox checks.
Keep up the great work.