diff options
author | Giovanni Mascellani <giovanni@mascellani.eu> | 2020-11-02 21:32:28 +0300 |
---|---|---|
committer | Arkadiusz Hiler <ahiler@codeweavers.com> | 2021-11-02 17:49:15 +0300 |
commit | 3ba1c093a5e6475bfe94e451d905709a7259ca04 (patch) | |
tree | b1c29bd468f8acdec91d6c605873270444fdef30 | |
parent | 74a40b17aa2003378bb48d2adb07d9bbe010d26b (diff) |
Stop processing Vagrantfile in case of errorsexperimental-bleeding-edge-6.3-2054-20211102-p3ba1c0-wa55a995-d1b1206-v35d2f1
If something in the provisioning of the vagrant virtual machine goes
wrong the developer might not notice (the creation log is very long),
but the virtual machine will be more or less subtly broken. Instead,
halting on errros makes problems immediately apparent.
Link: https://github.com/ValveSoftware/Proton/pull/4343
-rw-r--r-- | Vagrantfile | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/Vagrantfile b/Vagrantfile index 6f871546..e684dc38 100644 --- a/Vagrantfile +++ b/Vagrantfile @@ -65,6 +65,7 @@ Vagrant.configure(2) do |config| debian10.vm.synced_folder ".", "/home/vagrant/proton", id: "proton", type: "rsync", rsync__exclude: ["vagrant_share"] debian10.vm.provision "shell", privileged: "true", inline: <<-SHELL + set -e #install docker and steam-runtime dependencies dpkg --add-architecture i386 apt-get update |