I had intended to build the image on a laptop with minimal disk space (say 5gb) and then increase disk space when uploading to ESXi (we need say 100gb). The issue with is that doing so does not automatically expand the LV to fill the space (any hints welcome else I'll look it up).
I can build on the server directly but I need to store the built images and keep them in, say, Nexus. Smaller is better... Anyhow, the floppy gave me an idea: how reasonable is it to have the machine built with static ip but such that if a floppy is present on boot that it copies over eth1-cfg with what's on disk and does a network restart? This would allow for post-configuration of the image depending on what's in the floppy mount per VM. Thanks, Martin -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/13767338-1018-431c-ae33-5b8ef1224318%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
