clone or install VM

Douglas Davenport

unread,

Jan 18, 2017, 1:16:04 PM1/18/17

to CoreOS User

What is the best practice for a new Container Linux VMWare VM

1) install new VM from .ova

2) clone an existing VM and reconfigure it

If #2 then what should be reconfigured besides hostname, IP, ssh, ...

Alex Crawford

unread,

Jan 18, 2017, 1:19:49 PM1/18/17

to Douglas Davenport, CoreOS User

The first option is definately preferred. You can leverage Ignition to
do any of the provisioning steps required (user account creation,
service creation, disk partitioning, filesystem formatting, etc.).

If you go with the second option, make sure to remove /etc/machine-id
before shutting down and cloning. You will want each machine to have
its own identity.

-Alex

signature.asc

Douglas Davenport

unread,

Jan 18, 2017, 1:22:07 PM1/18/17

to CoreOS User

got it, thanks

Mimmus

unread,

Mar 2, 2017, 4:35:17 AM3/2/17

to CoreOS User, douglas.d...@gmail.com

Il giorno mercoledì 18 gennaio 2017 19:19:49 UTC+1, Alex Crawford ha scritto:

On 01/18, Douglas Davenport wrote:
>> What is the best practice for a new Container Linux VMWare VM
>>
>> 1) install new VM from .ova
>>
>> 2) clone an existing VM and reconfigure it
>>
>> If #2 then what should be reconfigured besides hostname, IP, ssh, ...

> The first option is definately preferred.

I converted a VM deployed from .ova to a VMware template and I'm deploying new VMs from this template by an automated Powershell script.
This seems working pretty well. Do you see some issue?

Reply all

Reply to author

Forward