I have a Linux VM that I am creating via the vagrant up command and then it gets provisioned via a bash shell script within a Vagrantfile as follows:
config.vm.define “ids7” do |x|
x.vm.box = “stig-rhel7-base”
x.vm.hostname=“ids7”
x.vm.network “private_network”, ip: “192.168.0.53”, virtualbox__intnet: “siem_ids”
x.vm.network “private_network”, ip: “192.168.14.210”, virtualbox__intnet: “monitored_network_1”
x.vm.network “private_network”, ip: “192.168.15.210”, virtualbox__intnet: “monitored_network_2”
x.vm.provision :shell, path: “vagrantsupport/ids7.sh”, args: “2>&1 | tee /vagrant/ids7_log_$(date +”‘%FT%H%M%z’“).txt”
end
I’ve intentionally modified my ids7.sh bash script to exit with a code of 1 to simulate an error in the provisioning, but it looks like this exit code does get returned by the ‘vagrant up ids7’ command.
I am using a Windows 10 host machine.
I am running ‘vagrant up ids7’ on a command prompt.
Anyone have an idea of how to capture the error?