VestaCP in LXC Container

mehargags

I stumbled upon some problems installing VestaCP control Panel inside an LXC container.

I tried with an Unprivileged Container ... it won't even install and even if it does, its more than 60% broken.

Installed fine on a Privileged Container ... but it doesn't really function properly.

Before I dive deep into the elements, I'd like to have any tips, tricks, custom configs that might have worked for someone who has used VestaCP in an LXC/Docker, so please share whatever knowledge you can over VestaCP install inside a Container.

Thanks alot

Log when trying to add a new domain in VestaCP (on Privlidged container)
https://pastebin.com/BsA0qe2T

TheXO

It works out of the box for me on proxmox + lxc, running centos 7 x64 (unprivileged)

both proxmox 5 / 4.4

agentmishra

these seems to be some isntallation issue
kindly check the repo and reinstall

mehargags

Ok... I resolved this too...
Need to do direct SSH into the container to be able to do this.

If I do lxc exec xenial /bin/bash or lxc-attach it doesn't allow me to install VestaCP. Looks like some kernel OS level access is not given when you ssh from within the host node.

I'm very new to proxmox... paving my way through.

I'm yet to try... but I think lxc-console -n lxcname -t 0 should also work ?

eva2000

why use LXC and not LXD ? I had very little problems using Ubuntu 18 and LXD containers with my ssdnodes KVM VPS for installing Centmin Mod LEMP stack on CentOS 7 and various other LEMP stacks https://community.centminmod.com/threads/nginx-http-2-https-benchmarks-centmin-mod-vs-easyengine-vs-webinoly-vs-vestacp-vs-oneinstack.14977/

Only problem was a bug in CentOS7 systemd version for setting open file descriptor limits within LXD containers - updating systemd version with Facebook RPM backports fixed it though see https://github.com/centminmod/centminmod-lxd

servertrading

I agree with eva2000. It can be more interesting for you to use LXD. And then you can couple it with proxmox or solusVM