Sounds like your vagrant box has an altered /etc/sudoers in there prior to you booting it and the bootstrap tried to upgrade sudo to a newer version causing dpkg to burp on it. (read: whoever made the box hasn’t heard of /etc/sudoers.d which was invented for this sort of thing)
There’s two ways to fix this I think: - Sanitize your box to not do the bad thing to /etc/sudoers or - Find out whatever argument the package installer needs to always answer “N” to that question and add it to the line in the bootstrap mechanism that calls it. I don’t remember it off the top of my head, but I dimly recall there being an envvar that can convince it. Chris. From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Connolly, Padraig Sent: Friday, November 04, 2016 12:37 To: vpp-dev@lists.fd.io Subject: [vpp-dev] Dpkg error during vagrant install Hi all, I am currently trying to build a fresh Vagrant VM within VPP (for testing purposes) but during the install I encounter this error.. ==> default: Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.30.7-0ubuntu1.6) ... ==> default: Errors were encountered while processing: ==> default: sudo ==> default: E: Sub-process /usr/bin/dpkg returned an error code (1) The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong. I also get this during ‘setting up’ stage: ==> default: Setting up sudo (1.8.9p5-1ubuntu1.3) ... ==> default: Configuration file '/etc/sudoers' ==> default: ==> Modified (by you or by a script) since installation. ==> default: ==> Package distributor has shipped an updated version. ==> default: What would you like to do about it ? Your options are: ==> default: Y or I : install the package maintainer's version ==> default: N or O : keep your currently-installed version ==> default: D : show the differences between the versions ==> default: Z : start a shell to examine the situation ==> default: The default action is to keep your current version. ==> default: *** sudoers (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package sudo (--configure): ==> default: EOF on stdin at conffile prompt Before this I was able to build the vagrant VM with no errors at all but now every time run ‘vagrant up’, it gives the above. I have also reinstalled sudo but it has made no difference. Has anyone encountered this and if so do you have a fix? All help will be much appreciated. Thanks, Padraig C
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
