Hi
I gave up running omv as lxc guest fit now because NFS will not run. Kernel space nfs does not work in lxc, and user space implementation lacks file lock feature. (It seems NFS has the same limitations in LXC as in openVZ.)
I remember collects cannot run in LXC. I found this may be due to /etc/hosts not set up properly (maybe if you rename container's hostname). If collect cannot start upon its installation some packages will not be configured, leaving the container in a unstable state.
Choose a name for your container before creating it. Create it : lxc-create (some args) -n container-name
Start your container and check its setup :
hostname -s
hostname -d
hostname -f
They should return respectively the short name of your container, the domain of your container and the fqdn of your container.
In /etc/hosts there is a line starting by 127.0.0.1
The names found in this line should be the the name of your container, its fqdn and literally localhost.
I'm not sure about the order of these 3 names, try to reorder them if you fail to restart collectd.
Apt a get install collectd
# fix /etc/hosts if still needed
service collected restart
apt-get install -f
#install OMV on top of jessie
# instructions available on the forum, easily found via Google.
For your information I prefer run OMV as hosts for my containers to ensure a fully working file server. I think this is a bad idea to make a block device available in a container, because this configuration depends on the order and the number of HDDs in the host. Adding a HDD may break things.
If you're interested I managed to install LXC, sssd and realmd from wheezy-backports without breaking OMV.
EDIT : realmd is not available in backports, it is available in jessie onwards.
