Changes
→Virtual Environment Setup
===== IPVS =====
Important! You have to turn on NET_ADMIN capability for container:
vzctl set $VEID --capability "NET_ADMIN:on" --save
Then restart the container
Install ipvsadm, then set all necessary modules to load at boot, and load them now.
Note: you probably don't need all of these, but I got sick of trying to find the minimal set and gave up :)
===== Bridge Utils =====
== Virtual Environment Setup ==
You can get real servers inside container running using veth interface connected to linux bridge. But problem is that real server inside container and virtual server (ipvs director) can not coexists in the same HN (hardware node) wherever ipvs reside either in the host or in the guest. The reason is that ipvs is not isolated in or from container and when ipip get unpacked it treated as if it come from client directly and go into ipvs handle again. This cause endless loop.