I've done it using more or less the same openvz recommended guidelines as you. My approach is that files are rsynced from physical server first, after you do necessary changes for container to boot, and then complete further openvz guidelines for standard template creation (e.g. service removal, first boot procedures) but the result should be the same. Parallels Virtuozzo feature "Migrate server to container" uses the same procedures.
Also i left the system state as much as possible to turnkey default, e.g. not updating packages, this is left for the user to decide whether to do updates himself or use turnkey auto-update.
What you can add to your procedures which is recommended, is to regenerate ssh keys on firstboot, or more useful run inithooks on boot, which takes care of ssh keys, ssl certs and other appliance specific actions.
On confconsole, I'm was more oriented to openvz provider environment where static ips are set outside of container (e.g. vzctl), so then confconsole becomes sufficient and can produce troubles in certain setups as you've said.
Hi I've done it using more or
Hi
I've done it using more or less the same openvz recommended guidelines as you. My approach is that files are rsynced from physical server first, after you do necessary changes for container to boot, and then complete further openvz guidelines for standard template creation (e.g. service removal, first boot procedures) but the result should be the same. Parallels Virtuozzo feature "Migrate server to container" uses the same procedures.
Also i left the system state as much as possible to turnkey default, e.g. not updating packages, this is left for the user to decide whether to do updates himself or use turnkey auto-update.
What you can add to your procedures which is recommended, is to regenerate ssh keys on firstboot, or more useful run inithooks on boot, which takes care of ssh keys, ssl certs and other appliance specific actions.
On confconsole, I'm was more oriented to openvz provider environment where static ips are set outside of container (e.g. vzctl), so then confconsole becomes sufficient and can produce troubles in certain setups as you've said.