gistfile1.txt

brian@localghost:triggers % be vagrant up                                                                ±[●][master]
You appear to be running Vagrant outside of the official installers.
Note that the installers are what ensure that Vagrant has all required
dependencies, and Vagrant assumes that these dependencies exist. By
running outside of the installer environment, Vagrant may not function
properly. To remove this warning, install Vagrant using one of the
official packages from vagrantup.com.

Bringing machine 'ubuntu' up with 'vmware_desktop' provider...
==> ubuntu: Running triggers before up ...
==> ubuntu: Running trigger...
==> ubuntu: only 1
==> ubuntu: Cloning VMware VM: 'bento/ubuntu-16.04'. This can take some time...
==> ubuntu: Checking if box 'bento/ubuntu-16.04' is up to date...
==> ubuntu: Verifying vmnet devices are healthy...
==> ubuntu: Preparing network adapters...
==> ubuntu: Starting the VMware VM...
==> ubuntu: Waiting for the VM to receive an address...
==> ubuntu: Forwarding ports...
    ubuntu: -- 22 => 2222
==> ubuntu: Waiting for machine to boot. This may take a few minutes...
    ubuntu: SSH address: 172.16.151.129:22
    ubuntu: SSH username: vagrant
    ubuntu: SSH auth method: private key
    ubuntu:
    ubuntu: Vagrant insecure key detected. Vagrant will automatically replace
    ubuntu: this with a newly generated keypair for better security.
    ubuntu:
    ubuntu: Inserting generated public key within guest...
    ubuntu: Removing insecure key from the guest if it's present...
    ubuntu: Key inserted! Disconnecting and reconnecting using new SSH key...
==> ubuntu: Machine booted and ready!
==> ubuntu: Configuring network adapters within the VM...
==> ubuntu: Waiting for HGFS to become available...
==> ubuntu: Enabling and configuring shared folders...
    ubuntu: -- /Users/brian/code/vagrant-sandbox/triggers: /vagrant
==> ubuntu: Running triggers after up ...
==> ubuntu: Running trigger...
==> ubuntu: Reloading VM...
    ubuntu: Running local: Inline script
    ubuntu: bundle exec vagrant reload
    ubuntu: You appear to be running Vagrant outside of the official installers.
    ubuntu: Note that the installers are what ensure that Vagrant has all required
    ubuntu: dependencies, and Vagrant assumes that these dependencies exist. By
    ubuntu: running outside of the installer environment, Vagrant may not function
    ubuntu: properly. To remove this warning, install Vagrant using one of the
    ubuntu: official packages from vagrantup.com.
    ubuntu: ==> ubuntu: Attempting graceful shutdown of VM...
    ubuntu: ==> ubuntu: Waiting for the VMX process to go away...
    ubuntu: ==> ubuntu: Checking if box 'bento/ubuntu-16.04' is up to date...
    ubuntu: ==> ubuntu: Verifying vmnet devices are healthy...
    ubuntu: ==> ubuntu: Preparing network adapters...
    ubuntu: WARNING: The VMX file for this box contains a setting that is automatically overwritten by Vagrant
    ubuntu: WARNING: when started. Vagrant will stop overwriting this setting in an upcoming release which may
    ubuntu: WARNING: prevent proper networking setup. Below is the detected VMX setting:
    ubuntu: WARNING:
    ubuntu: WARNING:   ethernet0.pcislotnumber = "32"
    ubuntu: WARNING:
    ubuntu: WARNING: If networking fails to properly configure, it may require this VMX setting. It can be manually
    ubuntu: WARNING: applied via the Vagrantfile:
    ubuntu: WARNING:
    ubuntu: WARNING:   Vagrant.configure(2) do |config|
    ubuntu: WARNING:     config.vm.provider :vmare_desktop do |vmware|
    ubuntu: WARNING:       vmware.vmx["ethernet0.pcislotnumber"] = "32"
    ubuntu: WARNING:     end
    ubuntu: WARNING:   end
    ubuntu: WARNING:
    ubuntu: WARNING: For more information: https://www.vagrantup.com/docs/vmware/boxes.html#vmx-whitelisting
    ubuntu: ==> ubuntu: Starting the VMware VM...
    ubuntu: ==> ubuntu: Waiting for the VM to receive an address...
    ubuntu: ==> ubuntu: Forwarding ports...
    ubuntu:     ubuntu: -- 22 => 2222
    ubuntu: ==> ubuntu: Waiting for machine to boot. This may take a few minutes...
    ubuntu:     ubuntu: SSH address: 172.16.151.129:22
    ubuntu:     ubuntu: SSH username: vagrant
    ubuntu:     ubuntu: SSH auth method: private key
    ubuntu: ==> ubuntu: Machine booted and ready!
    ubuntu: ==> ubuntu: Configuring network adapters within the VM...
    ubuntu: ==> ubuntu: Waiting for HGFS to become available...
    ubuntu: ==> ubuntu: Enabling and configuring shared folders...
    ubuntu:     ubuntu: -- /Users/brian/code/vagrant-sandbox/triggers: /vagrant
    ubuntu: ==> ubuntu: Machine already provisioned. Run `vagrant provision` or use the `--provision`
    ubuntu: ==> ubuntu: flag to force provisioning. Provisioners marked to run always will still run.
    ubuntu: ==> ubuntu: Running triggers after reload ...
    ubuntu: ==> ubuntu: Running trigger...
    ubuntu: ==> ubuntu: Running script...
    ubuntu:     ubuntu: Running: /var/folders/nf/pw544nm16fd9gf33kp04047r0000gn/T/vagrant-shell20180417-3723-17nrilm.sh
    ubuntu:     ubuntu: Linux vagrant 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Vagrantfile

# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
  config.vm.box = "bento/ubuntu-16.04"

  config.trigger.after :up,
    info: "Reloading VM...",
    run: {inline: "bundle exec vagrant reload"}

  config.trigger.after :reload do |trigger|
    trigger.info =  "Running script..."
    trigger.run_remote = {path: "script.sh"}
  end

  config.vm.define "ubuntu" do |m|
    m.vm.box = "bento/ubuntu-16.04"
    m.trigger.before :up, {info: "Hello world!"}
  end
end