| Summary: | Concerns about FreeBSD Vagrant boxes | ||
|---|---|---|---|
| Product: | Services | Reporter: | Guangyuan Yang <ygy> |
| Component: | Core Infrastructure | Assignee: | FreeBSD Release Engineering <re> |
| Status: | Closed Overcome By Events | ||
| Severity: | Affects Many People | CC: | emaste, gjb, re, ygy |
| Priority: | --- | ||
| Version: | unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Guangyuan Yang
2017-11-06 13:54:45 UTC
(In reply to Guangyuan Yang from comment #0) > I am trying out FreeBSD Vagrant boxes. I do have several concerns that I > could not find the answer anywhere: > > 1. The default login user is vagrant (passwd:vagrant), while I cannot login > as root. What is the default password for root? (and can we document this > somewhere?) > The root user does not have a default password. Obtaining root access is done with sudo. (This is a Vagrant-specific configuration, not FreeBSD.) > 2. Confusions about Vagrantfile has been raised over the Internet[1]. While > instructions are posted[2], is it possible to add this configuration to the > official page[3]? > Invoking 'vagrant up' a second time will boot correctly, with a random generated MAC. This is documented in the 10.4-RELEASE errata page, but apparently missed in the 11.1-RELEASE errata page. I'll add it. https://www.freebsd.org/releases/10.4R/errata.html Adding a static MAC to the release tools will likely cause problems when multiple Vagrant boxes are running on the same network. Adding random generated MAC addresses to the build tools > 3. The latest security/sudo has a known bug: while hostname was not defined, > sudo will immediately encounter segfault (see PR222510[4]). Is it beneficial > to consider adding a default hostname for Vagrant boxes? > This was added last week in r325156 to 12-CURRENT. The MFC is not done yet. A commit references this bug: Author: gjb Date: Mon Nov 6 17:27:50 UTC 2017 New revision: 325489 URL: https://svnweb.freebsd.org/changeset/base/325489 Log: Document issuing 'vagrant up' a second time will boot properly if the virtual machine does not yet have a MAC address. PR: 223474 (related) Sponsored by: The FreeBSD Foundation Changes: stable/11/release/doc/en_US.ISO8859-1/errata/article.xml A commit references this bug: Author: gjb Date: Mon Nov 6 17:29:00 UTC 2017 New revision: 51183 URL: https://svnweb.freebsd.org/changeset/doc/51183 Log: Regen after r325489. PR: 223474 (related) Sponsored by: The FreeBSD Foundation Changes: head/en_US.ISO8859-1/htdocs/releases/11.1R/errata.html (In reply to Glen Barber from comment #1) > (In reply to Guangyuan Yang from comment #0) > > I am trying out FreeBSD Vagrant boxes. I do have several concerns that I > > could not find the answer anywhere: > > > > 1. The default login user is vagrant (passwd:vagrant), while I cannot login > > as root. What is the default password for root? (and can we document this > > somewhere?) > > > > The root user does not have a default password. Obtaining root access is > done with sudo. (This is a Vagrant-specific configuration, not FreeBSD.) > > > 2. Confusions about Vagrantfile has been raised over the Internet[1]. While > > instructions are posted[2], is it possible to add this configuration to the > > official page[3]? > > > > Invoking 'vagrant up' a second time will boot correctly, with a random > generated MAC. This is documented in the 10.4-RELEASE errata page, but > apparently missed in the 11.1-RELEASE errata page. I'll add it. > > https://www.freebsd.org/releases/10.4R/errata.html > > Adding a static MAC to the release tools will likely cause problems when > multiple Vagrant boxes are running on the same network. Adding random > generated MAC addresses to the build tools > This last sentence is incomplete. It should have read: Adding random generated MAC addresses to the build tools breaks build reproducibility. > > 3. The latest security/sudo has a known bug: while hostname was not defined, > > sudo will immediately encounter segfault (see PR222510[4]). Is it beneficial > > to consider adding a default hostname for Vagrant boxes? > > > > This was added last week in r325156 to 12-CURRENT. The MFC is not done yet. (In reply to Glen Barber from comment #4) Thanks! This PR did clear things up. Now my only concern is - some boxes would be unusable before the MFC period ends. I think it is safe to close this PR now. |