I am using Proxmox. Is there any reason why it would be better to avoid installing Carbonio in an LXC container?
I use plain Ubuntu server and I've installed it inside a privileged ubuntu LXC container. I tried it first using unprivileged container, but that did not work well - installation of packages went ok, but bootstrapping failed for me.
I see no reason why it would not work well in a container. I assume it won't be long before they switch to non-lxc containers (docker-like).
I see no reason why it would not work well in a container
Thank you @AtuM
FTR consul services discovery just doesn't work on a CT with LXC.
I have done many many many tests with privileged and unprivileged CT's and no matter what you do it always fail with "Error connecting to Consul agent: Unexpected response code: 403 (Permission denied)" messages in almost all "carbonio-services"
So, my suggestion is to still avoid CT's
@anahuac Greetings friend, the same thing happens to me since I started testing carbonio using LXC in proxmox, has found a solution to this problem, since without this consul service many others fail in carbonio.
Aug 23 12:03:02 correo systemd[1]: Started Carbonio Files sidecar proxy.
Aug 23 12:03:02 correo consul[64953]: Error connecting to Consul agent: Unexpected response code: 403 (Permission denied)
@anahuac is not easy. Having to install everything again in a VM the O.S. What a problem this is, with Zimbra these things have never happened to me. Thank you.
Well... expect that all work on Carbonio as the same way it worked in Zimbra is a mistake. Most things might, but not all. Those are two different softwares.
Take it in the the good way: now you know better.