It doesn't actually not a good fit. Packer starts a VM and provision
the config on it and then saves a snapshot of that VM. A installable
ISO contains data and program that installs the data onto a new
machine. That is a very different process.
And creating a auto-installing ISO from a standard CentOS image is just:
1) unpack the ISO to writable directory
2) add a kickstart file
3) edit the default boot loader command to load that kickstart file
4) pack everything up in a new ISO
(This process can be done in a Packer template using the artifice
post-processor if you want to automate this procedure and run it in a
isolated environment).
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
>
https://www.hashicorp.com/community-guidelines.html. Behavior in violation
> of those guidelines may result in your removal from this mailing list.
>
> GitHub Issues:
https://github.com/mitchellh/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Packer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
packer-tool...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/packer-tool/9ad2cc91-5c55-44b4-8e63-db082f0716b3%40googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.