iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

update docs for headless to help users know they may need to launch the gui

This commit is contained in:
Megan Marsh 2020-04-08 13:53:19 -07:00
parent e845632d3d
commit a48c0ecf49
2 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
builder/vmware/common/run_config.go
View File

@ -14,6 +14,11 @@ type RunConfig struct {
// this value is set to true, the machine will start without a console. For // this value is set to true, the machine will start without a console. For
// VMware machines, Packer will output VNC connection information in case you // VMware machines, Packer will output VNC connection information in case you
// need to connect to the console to debug the build process. // need to connect to the console to debug the build process.
// Some users have experienced issues where Packer cannot properly connect
// to a VM if it is headless; this appears to be a result of not ever having
// launched the VMWare GUI and accepting the evaluation license, or
// supplying a real license. If you experience this, launching VMWare and
// accepting the license should resolve your problem.
Headless bool `mapstructure:"headless" required:"false"` Headless bool `mapstructure:"headless" required:"false"`
// The IP address that should be // The IP address that should be
// binded to for VNC. By default packer will use 127.0.0.1 for this. If you // binded to for VNC. By default packer will use 127.0.0.1 for this. If you

5
website/pages/partials/builder/vmware/common/RunConfig-not-required.mdx
View File

@ -5,6 +5,11 @@
this value is set to true, the machine will start without a console. For this value is set to true, the machine will start without a console. For
VMware machines, Packer will output VNC connection information in case you VMware machines, Packer will output VNC connection information in case you
need to connect to the console to debug the build process. need to connect to the console to debug the build process.
Some users have experienced issues where Packer cannot properly connect
to a VM if it is headless; this appears to be a result of not ever having
launched the VMWare GUI and accepting the evaluation license, or
supplying a real license. If you experience this, launching VMWare and
accepting the license should resolve your problem.
- `vnc_bind_address` (string) - The IP address that should be - `vnc_bind_address` (string) - The IP address that should be
binded to for VNC. By default packer will use 127.0.0.1 for this. If you binded to for VNC. By default packer will use 127.0.0.1 for this. If you