Jeremy Davis's picture

Beat me to it! This is something I've had in mind for a while, but another thing I just haven't got around to yet... Actually I was considering producing a generic script that users could use on any TKL appliance to create their own OpenVZ template, but I abandoned that because I'm not a great scripter and with error handling etc, it was just getting bigger and more painful to use.

Sounds like you know your way around OpenVZ!? Are there any other tweaks you've made to the templates? How does your conversion from .iso to OpenVZ template compare to the instructions I posted on the Dev Wiki? I'd be really interested to hear as I'm a real Linux noob and bashed those instructons together through lots of reading and trial and error and (somehow) managed to get it all working very nicely.

Also for your interest, I have found that I can use confconsole fine if I allow my template to get assigned IPs via DHCP, whereas it is useless if I hardcode the IP with OpenVZ (confconsole tries to configure the wrong interface). For most appliances I use a hardcoded IP but I noticed some things don't play nice with a hardcoded IP when inside an OpenVZ container (eg BIND9) and will only work with a DHCP supplied address. I used the confconsole to get around that and set a static IP (although I know I could've just edited the config file).