[Bug 213858] Vagrant image freebsd/FreeBSD-11.0-RELEASE-p1 missing sudo

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Oct 28 16:37:01 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213858

            Bug ID: 213858
           Summary: Vagrant image freebsd/FreeBSD-11.0-RELEASE-p1 missing
                    sudo
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: misc
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: jwhulette at gmail.com
                CC: freebsd-amd64 at FreeBSD.org
                CC: freebsd-amd64 at FreeBSD.org

When bring up the vm, it errors out that sudo is not installed. I can log in
using vagrant ssh and su to root.

Bringing machine 'freebsd11' up with 'virtualbox' provider...
==> freebsd11: Importing base box 'freebsd/FreeBSD-11.0-RELEASE-p1'...
==> freebsd11: Matching MAC address for NAT networking...
==> freebsd11: Checking if box 'freebsd/FreeBSD-11.0-RELEASE-p1' is up to
date...
==> freebsd11: Setting the name of the VM:
formsmooreandscarrycom_freebsd11_1477670941466_65674
==> freebsd11: Clearing any previously set network interfaces...
==> freebsd11: Preparing network interfaces based on configuration...
    freebsd11: Adapter 1: nat
    freebsd11: Adapter 2: hostonly
==> freebsd11: Forwarding ports...
    freebsd11: 80 (guest) => 8080 (host) (adapter 1)
    freebsd11: 22 (guest) => 2222 (host) (adapter 1)
==> freebsd11: Running 'pre-boot' VM customizations...
==> freebsd11: Booting VM...
==> freebsd11: Waiting for machine to boot. This may take a few minutes...
    freebsd11: SSH address: 127.0.0.1:2222
    freebsd11: SSH username: vagrant
    freebsd11: SSH auth method: private key
    freebsd11: Warning: Remote connection disconnect. Retrying...
    freebsd11: Warning: Remote connection disconnect. Retrying...
    freebsd11: Warning: Remote connection disconnect. Retrying...
    freebsd11: Warning: Remote connection disconnect. Retrying...
    freebsd11: Warning: Remote connection disconnect. Retrying...
    freebsd11: Warning: Remote connection disconnect. Retrying...
    freebsd11: Warning: Remote connection disconnect. Retrying...
    freebsd11:
    freebsd11: Vagrant insecure key detected. Vagrant will automatically
replace
    freebsd11: this with a newly generated keypair for better security.
    freebsd11:
    freebsd11: Inserting generated public key within guest...
    freebsd11: Removing insecure key from the guest if it's present...
    freebsd11: Key inserted! Disconnecting and reconnecting using new SSH
key...
==> freebsd11: Machine booted and ready!
Sorry, don't know how to check guest version of Virtualbox Guest Additions on
this platform. Stopping installation.
==> freebsd11: Checking for guest additions in VM...
    freebsd11: The guest additions on this VM do not match the installed
version of
    freebsd11: VirtualBox! In most cases this is fine, but in rare cases it can
    freebsd11: prevent things such as shared folders from working properly. If
you see
    freebsd11: shared folder errors, please make sure the guest additions
within the
    freebsd11: virtual machine match the version of VirtualBox you have
installed on
    freebsd11: your host and reload your VM.
    freebsd11:
    freebsd11: Guest Additions Version: 4.3.38
    freebsd11: VirtualBox Version: 5.1
==> freebsd11: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ifconfig -a | grep -o ^[0-9a-z]* | grep -v '^lo'

Stdout from the command:



Stderr from the command:

sudo: Command not found.

vagrant version
Installed Version: 1.8.6
Latest Version: 1.8.6

vboxmanage --version
5.1.8r111374

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list