-
Notifications
You must be signed in to change notification settings - Fork 9.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vagrant up
build: multiple errors upgrading packages, installing prereqs, setting up go
#9763
Comments
@steven-collins-omega hi there! I am sorry that your are having issues. Let me look into fixing this. |
I'm having the exact same issue, in the same sudoers configuration file. Looks like we need an auto confirm flag for reinstalling the config files if it is modified by some script and this option pops up. |
@Aseemraj hi there! Sorry to about the issues! Yes, precisely, we need to accept upstream configuration changes to the files which are normally set to be protected by the package maintainers. |
@kwilczynski I think in the vagrant file, wherever we have apt-get update and upgrade, we can use one of these flags:
This line can include these additional options and it should be good to go as I figure. |
@steven-collins-omega @Aseemraj hi there! Apologies for the delay. I have opened a Pull Request that contains fixes which should resolve this issue. |
Closed via #9783 |
The dpkg sudo trigger appears to want to run interactively despite the noninteractive debconf setting. This is a problem upstream for vagrant also, see. hashicorp/terraform#9763 Incorporating the recommended fix to Vagrantfile from upstream hashicorp/terraform#9783 Change-Id: I8da8522fc9e80fc3bd268b347a786054ad019170 Signed-off-by: Ray Kinsella <ray.kinsella@intel.com>
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Expected Behavior
What should have happened?
A Vagrant box with a working build environment should have been set up.
Actual Behavior
What actually happened?
go
and related tools are not installed correctly:Steps to Reproduce
Simply follow the instructions in BUILDING.md.
Important Factoids
Here is the last part of the output of
vagrant up
:References
git bisect
indicates that this failure was introduced at PR #8762.The text was updated successfully, but these errors were encountered: