[pve-devel] Create template from CT
James A. Coyle
james.coyle at jamescoyle.net
Tue Mar 4 12:20:13 CET 2014
> Dietmar, it looks like a backup file is not the same as a template file for a CT -
> is that not correct? For example, the backup file contains config and literally
> everything from the CT root. A template is not the same, it does not contain
> config
>why not?
Well where does the proxmox config come from in a vzdump? I assume it has to be in there somewhere? Looking further into it, other items need removing too which could be added to an excludes list in the tar command.
> and I suspect that other things may need removing too - such as
> networks, /tmp, etc. I need some more information on what the exact
> differences are and we may need to consider the CT OS distribution type. In
> addition, it lands in the cache dir of the storage device so that no manual
> intervention is required.
>Sure. But there is currently no real standard which defines what a template
>should contain or not. So automatic creation is out of scope unless there is a well-defined standard.
>For now, we use DAB to create templates.
DAB does not meet my needs - I spend a lot of time installing software which is not in a repo and has to be manually installed. So are you saying that because there is nothing written down on OpenVZ, Proxmox will not support this feature? I basically want to create a template from an existing CT.
More information about the pve-devel
mailing list