Open chrisjsewell opened 3 years ago
If possible @borellim, It would be good if you could try narrowing down what ones need to be added, e.g. a classic bisection approach; add half of them to tox.ini, run vagrant destroy
then tox -e vagrant
and see if you still get the error, rinse and repeat
Thanks to feedback by @borellim, it appears that there is an issue running
tox -e vagrant
on Linux, whereby it does not propagate the required environmental variables, and you end up with:To ensure environment isolation, tox only propagates a number of core environmental variables, and then anything you specify in
passenv
. Currently, this set up works on Mac but apparently not LinuX:Now you can set
passenv = *
, to pass all environmental variables, and this "fixed" it for @borellim. But it would be ideal to identify the exact additional variables that need to be passed.@borellim provided this list of environmental variable names he had in the parent terminal: