I can get as far as taking a snapshot of an antlet and creating a new template from that antlet. But, when I attempt to create a fresh antlet using the new template, it generates all new network MAC addresses for the new antlet. But the template has the original network MAC addresses imbedded in the image. So, when you boot the new antlet, both eth0 and eth1 fail because of the mismatches on the new MAC addresses. Is there an automated way to fix this. We need to generate dozens of antlets. As best I recall, this was handled automatically with VirtualBox and VMware using a simple checkbox when you created the new virtual machine.
I can get as far as taking a snapshot of an antlet and creating a new template from that antlet. But, when I attempt to create a fresh antlet using the new template, it generates all new network MAC addresses for the new antlet. But the template has the original network MAC addresses imbedded in the image. So, when you boot the new antlet, both eth0 and eth1 fail because of the mismatches on the new MAC addresses. Is there an automated way to fix this. We need to generate dozens of antlets. As best I recall, this was handled automatically with VirtualBox and VMware using a simple checkbox when you created the new virtual machine.