Thanks for the feedback Daniel. I'll look at the build instructions when I'm back at home.
The API can easily be changed and on reflection I agree. I'm not sure if the network needs to be removed - I was only following the manual build instructions which state to manually remove it. I suspect that what actually needs to happen is that some files need to be excluded, such as interfaces and hosts but I'll need to look more into it. 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 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. James Coyle M:+44 (0) 7809 895 392 E: [email protected] Skype: jac2703 Gtalk: [email protected] www: www.jamescoyle.net ----- Original Message ----- From: "Dietmar Maurer" <[email protected]> To: "James A. Coyle" <[email protected]>, [email protected] Sent: Monday, 3 March, 2014 6:14:10 AM Subject: RE: Create template from CT > I have made a few changes to the web GUI to add a new option under the > container context menu to make a template from a stopped container and > wanted to know if you would consider including it in the main distribution? This is basically the same as 'Backup' - so what are the advantages? _______________________________________________ pve-devel mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
