Am 17.12.2019 18:09 schrieb Stuart Henderson:
Without it, it will work if you already have the files locally but will
fail if it has to download them (make clean=dist).
Gotcha..
Problems I ran into (I don't think they should block the import but
would be good to handle them better in an update) :
- I typo'd the path to the iso file which resulted in this,
it would be nice to print the error message coming from vmctl which
would
have made it obvious what was going on.
Yep, some more possible error paths in there which are not handled yet.
- probably the builder can't do anything about it, but if you're
running
a web server on port 80 on the host running packer build, and if it
serves install.conf, bsd.rd will fetch that and won't go on to ask
"Response file location?", so the file that the builder is trying to
serve is never fetched.
That's a feature ;-) The point of the internal httpd was providing a
fallback
when you do not have a reachable webserver. If you remove the
'http_directory' from the JSON, packer won't even start one.
- seems to need doas "nopass" access to /usr/sbin/vmctl, I tried
without
and things don't seem right with the automated "keyboard" entry to the
vm.
Yes, that's the way how the plugin types into the VM; same goes for the
output - thus myvm.log is being created since a second console does not
work on OpenBSD. I've been pointing this out in my talks, but...
Maybe it's worth adding some small doc or pkg-readme file to mention
these.
I'll add some caveats excerpt upstream and handle it in post-install
like the
others.
Thanks a ton!
--
pb
