Packer: add custom floppy size in config for all builders

Created on 10 Mar 2016  路  4Comments  路  Source: hashicorp/packer

Now, the default floppy size is 14401024, it's enough sometime.
But, in some special cases we want to add some other files bigger than 1440
1024, such as compiled open-vm-tools and so on.
Yes, we can add files in provisions, but I think the size should be customize.

buildeparallels buildeqemu buildevirtualbox buildevmware enhancement pre-1.0 wontfix

Most helpful comment

The floppy part is to bootstrap the installation of the OS, pass Kickstart/preseed/unattended file and get the installation running.

So as today to put files into the new VM you can use the http server, or file provisioner.

Perhaps, add a feature create and mount an iso would be better than make a floppy large.
ie: https://github.com/johto/iso9660wrap

All 4 comments

An other solutions:
Before create floppy, calculate the size of all files and directories
If, the size is less than 1.44MB, create a 1.44MB size floppy, or create the size calculated before.

The floppy part is to bootstrap the installation of the OS, pass Kickstart/preseed/unattended file and get the installation running.

So as today to put files into the new VM you can use the http server, or file provisioner.

Perhaps, add a feature create and mount an iso would be better than make a floppy large.
ie: https://github.com/johto/iso9660wrap

Yes, create and mount an iso is the better solutions. Because the floppy big than 1.44Mb in vmware esx server is not available @rickard-von-essen

Would be happy to take a look at any PR that comes in for this.

However, this has low chance of being a priority for us anytime soon, so we'd rather close this issue than have it stagnate for more years to come. The best way to get this implemented would be to submit a PR. If you do so, we'd welcome this work. If you want to discuss how to go about doing this, feel free to reach out. I can help answer questions and do pre-reviews.

The reason we're more aggressively closing these issues at the moment is because we're pushing towards a 1.0 release, and reviewing all open issues as part of that process. Please see the mailing list for more details on 1.0.

Again, just want to say thank you for suggesting this and I DO think its a reasonable idea. But, since this is a feature request, it requires some work to add it to the project and we don't plan on doing that soon. But as this is also an open source project we welcome contributions. Thanks!

Was this page helpful?
0 / 5 - 0 ratings