Bug 212452 - vagrant image does not contain sudo when behind proxy
Summary: vagrant image does not contain sudo when behind proxy
Status: Closed Works As Intended
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: 10.3-STABLE
Hardware: Any Any
: --- Affects Only Me
Assignee: Brad Davis
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-07 11:27 UTC by Pierre Tardy
Modified: 2016-09-18 18:10 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre Tardy 2016-09-07 11:27:28 UTC 
Generated vagrant images does not contain the sudo package.

It does contain a /usr/local/etc/sudoers file, but no sudo

so there is no way to get root unless reboot in singleuser mode
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2016-09-11 01:35:41 UTC 
brd, is this something that you are working on?
Comment 2 Pierre Tardy 2016-09-11 07:56:20 UTC 
after more investigation and discussion with brd at https://github.com/brd/packer-freebsd/issues/17 , it looks like the problem comes with firstboot_pkgs_list which does not work behind proxy.

I keep my last suggestion of installing the firstboot_pkg at build time. This will greatly help imho fully automated vagrant workflow behind proxy.

I am not fully aware of the details and I would understand it is not practical.
Comment 3 Brad Davis freebsd_committer freebsd_triage 2016-09-18 18:10:19 UTC 
The take away is we don't really want to do this because then the packages installed will be very old as the RELEASE images age.

For users affected by this, I recommend they use the packer recipe and modify it to set the http_proxy env variable as part of the vagrant build.