somewhere but I don't understand how. Setting environment variables inside the host is tricky and doesn't (always?) percolate through a sudo because that effectively starts a new shell. This https://github.com/gosuri/vagrant-env may be the big-hammer solution to it, where the small hammer is to prefix every single apt-line in the Vagrantfile with that export. I'm not sure.
This doesn't seem to be hurting anything that I can observe; I'm just trying to make Vagrant load more cleanly overall.
ivoysey
commented
7 years ago
the message
gets printed several times every time you vagrant up. it's because different apt related things are assuming they're at a real interactive terminal but they aren't. per http://serverfault.com/questions/500764/dpkg-reconfigure-unable-to-re-open-stdin-no-file-or-directory, the fix is to include
somewhere but I don't understand how. Setting environment variables inside the host is tricky and doesn't (always?) percolate through a
sudobecause that effectively starts a new shell. This https://github.com/gosuri/vagrant-env may be the big-hammer solution to it, where the small hammer is to prefix every single apt-line in theVagrantfilewith that export. I'm not sure.This doesn't seem to be hurting anything that I can observe; I'm just trying to make Vagrant load more cleanly overall.