Greetings, ----- Original Message ----- > Most of the complaints stem around compromised instances, or bad yum > repo definitions or non managed / non manageable content being > included in the instance content etc. So it would be good to start with a > solid instance (template ?) and try to promote that.
The OpenVZ Project hasn't released any OS Templates with those issues to the best of my knowledge. If someone is claiming otherwise, I'd love to hear about it. I believe there are a large number of hosting providers that use OpenVZ... that use OS Templates that they have come up with themselves and offer to their customers. I imagine that might be where the these issues lie but I'm only guessing. A project named Proxmox VE integrated OpenVZ (along with KVM) for 8-9 years but with their most recent release they have switched to LXC. The reason I bring them up is because they also offered their own OS Templates as well as "application templates"... and would be the primary OS Template provider for Proxmox VE users. Again, to the best of my knowledge, the OpenVZ project has only ever offered OS Templates that were 99.9% stock distro packages... with the remaining 0.01% an OpenVZ provided package that typically did some minor config change to make the container start up with less resource requirements. TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work] _______________________________________________ Devel mailing list [email protected] https://lists.openvz.org/mailman/listinfo/devel
