geerlingguy/packer-centos-7

This build has been moved - see README.md

Packer Build - CentOS 7 minimal Vagrant Box

DEPRECATED: This Packer build has been moved to a new consolidated project: https://github.com/geerlingguy/packer-boxes

The public box is still available and updated on Vagrant Cloud: geerlingguy/centos7, but the build configuration has been moved to the consolidated project.

packer-centos-7's Issues

ssh hangs on centos7 version 1.1.4

Tried to start a new DrupalVM box up using geerlingguy/centos7 1.1.4 and kept getting hung at the point where ssh logins occur. No error messages would show either, it would just sort of hang for a while and then exit out saying it couldn't get ssh access. I am assuming this is a problem with the 1.1.4 release because when I made a Vagrantfile.local and added the following line, destroyed and ran up again, it was able to execute ssh.

config.vm.box_version = "1.1.3"

See geerlingguy/drupal-vm#960

Add 'Hyper-V' Builder

I am not a Vagrant expert (not really even a novice, tbh), but it would be nice to be able to have a Hyper-V version of this to build off of.

Add 'deltarpm' to minimize size of downloads on 'yum update'

Be convenient if the 'deltarpm' package were installed by default.

I'm using this with vagrant, and first thing I do when I create the box is 'yum update'... with deltarpm installed, it saves ~37mb of bandwidth.

Not a big deal as obviously I can instead do 'yum install deltarpm', 'yum update' but it would be handy.

Use Ansible requirements file rather than a bunch of manual steps.

NAT interface have same IP address on all virtualbox machine

Hello
I use https://vagrantcloud.com/geerlingguy/boxes/centos7/versions/1.2.16/providers/virtualbox.box in terraform-provider-virtualbox.
Run a few nodes:
Terraform config

resource "virtualbox_vm" "node" {
  count     = 3
  name      = format("node%02d", count.index + 1)
  image     = "virtualbox.box"
  cpus      = 1
  memory    = "2048 mib"

  network_adapter {
    type = "nat"
  }

  network_adapter {
    type           = "hostonly"
    host_interface = "vboxnet1"
  }

}```

But NAT interface have equal IP address on all virtualbox machine
terraform show

virtualbox_vm.node[0]:

resource "virtualbox_vm" "node" {
cpus = 1
id = "8bf98ea2-8492-45d5-979e-8ad8938bf2c2"
image = "virtualbox.box"
memory = "2.0 gib"
name = "node01"
status = "running"

network_adapter {
    device                 = "IntelPro1000MTServer"
    ipv4_address           = "10.0.2.15"
    ipv4_address_available = "yes"
    mac_address            = "08002785549C"
    status                 = "up"
    type                   = "nat"
}
network_adapter {
    device                 = "IntelPro1000MTServer"
    host_interface         = "vboxnet1"
    ipv4_address           = "192.168.57.3"
    ipv4_address_available = "yes"
    mac_address            = "080027265D28"
    status                 = "up"
    type                   = "hostonly"
}

}

virtualbox_vm.node[1]:

resource "virtualbox_vm" "node" {
cpus = 1
id = "620a7195-4e1b-49be-8295-13739352f4d4"
image = "virtualbox.box"
memory = "2.0 gib"
name = "node02"
status = "running"

network_adapter {
    device                 = "IntelPro1000MTServer"
    ipv4_address           = "10.0.2.15"
    ipv4_address_available = "yes"
    mac_address            = "08002795B91B"
    status                 = "up"
    type                   = "nat"
}
network_adapter {
    device                 = "IntelPro1000MTServer"
    host_interface         = "vboxnet1"
    ipv4_address           = "192.168.57.6"
    ipv4_address_available = "yes"
    mac_address            = "080027F6A8B9"
    status                 = "up"
    type                   = "hostonly"
}

}

virtualbox_vm.node[2]:

resource "virtualbox_vm" "node" {
cpus = 1
id = "ab2e09b6-8993-4445-afd5-467beecca59d"
image = "virtualbox.box"
memory = "2.0 gib"
name = "node03"
status = "running"

network_adapter {
    device                 = "IntelPro1000MTServer"
    ipv4_address           = "10.0.2.15"
    ipv4_address_available = "yes"
    mac_address            = "08002724A15B"
    status                 = "up"
    type                   = "nat"
}
network_adapter {
    device                 = "IntelPro1000MTServer"
    host_interface         = "vboxnet1"
    ipv4_address           = "192.168.57.5"
    ipv4_address_available = "yes"
    mac_address            = "080027F9123D"
    status                 = "up"
    type                   = "hostonly"
}

}

node3

[root@node3 ~]# ip a
3: enp0s17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 08:00:27:24:a1:5b brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global noprefixroute dynamic enp0s17
valid_lft 81822sec preferred_lft 81822sec
inet6 fe80::ffc3:fb7e:5052:c8bd/64 scope link noprefixroute
valid_lft forever preferred_lft forever

node2

[root@node2 ~]# ip a
3: enp0s17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 08:00:27:95:b9:1b brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global noprefixroute dynamic enp0s17
valid_lft 81806sec preferred_lft 81806sec
inet6 fe80::9a82:5804:2bcf:571b/64 scope link noprefixroute
valid_lft forever preferred_lft forever

How get different ip?

Push an updated box to https://atlas.hashicorp.com/geerlingguy/boxes/centos7 ??

Appreciate you making this available. I use your pre-built box here: https://atlas.hashicorp.com/geerlingguy/boxes/centos7

Unfortunately, when I vagrant up, the plugin https://github.com/dotless-de/vagrant-vbguest fails (more accurately, it correctly jumpstarts the guest additions build, but the build itself fails). When I SSH in and run yum update, and then reboot the box, the guest additions install works correctly. So something in the base box is outdated and causing the guest additions build to fail.

It looks like there's a few commits to this github repo that updated the CentOS build and EPEL version, but they haven't been pushed to the the pre-built base box... I have a hunch they might fix this issue that I'm hitting.

Mind pushing a new version up to Atlas?

`ansible up` == default: Warning: Connection timeout. Retrying...

Moved from geerlingguy/ansible-for-devops#54

Host Ubuntu 14.04, ansible 2.2.0.0, vboxmanage 4.3.36_Ubuntur105129

When doing an ansible up I get a

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'geerlingguy/centos7'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'geerlingguy/centos7' is up to date...
==> default: Setting the name of the VM: vagrant_default_1488056506230_50292
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 => 2222 (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...

This answer to use the GUI prompt to choose default|safe mode does get me past that stage. http://stackoverflow.com/a/22575302/292408.

config.vm.provider :virtualbox do |vb|
  vb.gui = true
end

In addition vagrant ssh doesn't appear to work, not sure if it is related or not.

CentOS 7.4 (1708) is here - update the image!

https://lists.centos.org/pipermail/centos-announce/2017-September/022532.html

virtualbox-iso: Timeout while waiting for machine to shut down.

Hey Jeff,

Did you ever run across an issue like shown below where shutdown fails and the artifact is removed (or never finalized)?

Host: MacOS latest
Guest: CentOS-7 (7.2.1511)

I tried several variations of shutdown_command. No change.
I tried a larger disk_size. No change.
Increased shutdown_timeout to 10m. No change.

What is weird is that I used this same setup and one of your packer-centos-6 packages just prior to this build attempt. No issues at all.

    virtualbox-iso: Installed size: 7.0 M
    virtualbox-iso: Downloading packages:
    virtualbox-iso: Running transaction check
    virtualbox-iso: Running transaction test
    virtualbox-iso: Transaction test succeeded
    virtualbox-iso: Running transaction
    virtualbox-iso: Erasing    : ansible-1.9.4-1.el7.noarch                                   1/1
    virtualbox-iso: Verifying  : ansible-1.9.4-1.el7.noarch                                   1/1
    virtualbox-iso:
    virtualbox-iso: Removed:
    virtualbox-iso: ansible.noarch 0:1.9.4-1.el7
    virtualbox-iso:
    virtualbox-iso: Complete!
    virtualbox-iso: dd: error writing ‘/EMPTY’: No space left on device
    virtualbox-iso: 49367+0 records in
    virtualbox-iso: 49366+0 records out
    virtualbox-iso: 51764068352 bytes (52 GB) copied, 97.2847 s, 532 MB/s
==> virtualbox-iso: Gracefully halting virtual machine...
==> virtualbox-iso: Timeout while waiting for machine to shut down.
==> virtualbox-iso: Unregistering and deleting virtual machine...
==> virtualbox-iso: Deleting output directory...
Build 'virtualbox-iso' errored: Timeout while waiting for machine to shut down.

==> Some builds didn't complete successfully and had errors:
--> virtualbox-iso: Timeout while waiting for machine to shut down.

==> Builds finished but no artifacts were created.

python-decorator issues

Appears to be some issues with the CentOS 7 box.

[root@salt-master ~]# firewall-cmd
Traceback (most recent call last):
  File "/bin/firewall-cmd", line 32, in <module>
    from firewall.client import *
  File "/usr/lib/python2.7/site-packages/firewall/client.py", line 29, in <module>
    import slip.dbus
  File "/usr/lib/python2.7/site-packages/slip/dbus/__init__.py", line 6, in <module>
    import service
  File "/usr/lib/python2.7/site-packages/slip/dbus/service.py", line 30, in <module>
    import polkit
  File "/usr/lib/python2.7/site-packages/slip/dbus/polkit.py", line 27, in <module>
    from decorator import decorator
ImportError: No module named decorator

A reinstall of certain packages fixes this issue:

[root@salt-master ~]# yum reinstall dbus-python pygobject3-base python-decorator python-slip-dbus python-decorator

And then:

[root@salt-master ~]# firewall-cmd
usage: see firewall-cmd man page
No option specified.

Can't mount native share shared directory

Just tried 1.2.1 in conjunction with DrupalVM and the provisioning bailed out early right when it attempts to mount shared folders. I rolled back to 1.2.0 and it worked fine.

DrupalVM 4.4.2
VirtualBox 5.1.20
Ansible 2.3
Vagrant 1.8.6 (edit)

Just wanted to report. Thanks!

Feature Request: Make this libVirt compatible

I am not sure what is required or how feasible it is to create vagrant images that work across providers

It would be nice if this image could work with the vagrant libvirt plugin, using QEMU/KVM as a backend, instead of virtualbox/vmware. I know that vbox is the goto standard, but the kvm implementation is much better on a linux host, as the filesharing can be done much better (with plan-9 fs overlay drivers)

Users using linux hosts have much better options for virtual machines than vbox, with much better core handling of VMs. Being forced to use box has great impact, as only one VM kernel driver can take control of the CPU vm architecture at a time.

https://github.com/vagrant-libvirt/vagrant-libvirt

Upgrade to Virtualbox Guest Additions 6.0

@geerlingguy 👍

Fetch cert with https

packer-centos-7/http/ks.cfg

Line 75 in 76469e0

wget -O/etc/pki/tls/certs/ca-bundle.crt http://curl.haxx.se/ca/cacert.pem

I recommend using https here.

Add Travis CI integration

Basically, validate the script to build the box, similar to what bento does: https://travis-ci.org/opscode/bento/builds/24882721

Add rsync to base install

Same justification as geerlingguy/packer-centos-6#5

VBoxGuestAdditions-5.1.20 in geerlingguy/centos7 v 1.2.1 has a broken symbolic link to mount.vboxsf. Unable to mount local filesystem into VM.

Summary

Issue seems to be a broken symlink within box geerlingguy/centos7 v 1.2.1. If you create a VM using geerlingguy/centos7 v1.2.1 you will not be able to mount /vagrant to the local filesystem where vagrant up was run.

Link to others with issue:
https://stackoverflow.com/questions/43492322/vagrant-was-unable-to-mount-virtualbox-shared-folders

dcastellani@dcastellani-mbp ~/D/g/d/vagrant> vagrant box list
centos/7            (virtualbox, 1703.01)
geerlingguy/centos7 (virtualbox, 1.2.1)

Example of issue

dcastellani@dcastellani-mbp ~/D/g/d/vagrant> vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'geerlingguy/centos7'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'geerlingguy/centos7' is up to date...
==> default: Setting the name of the VM: vagrant_default_1497965107575_73585
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Remote connection disconnect. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
    default: /vagrant => /Users/dcastellani/Documents/git/dcastellani_infra/vagrant
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:
 
mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant
 
The error output from the command was:
 
mount: wrong fs type, bad option, bad superblock on vagrant,
       missing codepage or helper program, or other error
 
       In some cases useful info is found in syslog - try
       dmesg | tail or so.

(1) dcastellani@dcastellani-mbp ~/D/g/d/vagrant> vagrant status
Current machine states:
 
default                   running (virtualbox)
 
The VM is running. To stop this VM, you can run `vagrant halt` to
shut it down forcefully, or you can run `vagrant suspend` to simply
suspend the virtual machine. In either case, to restart it again,
simply run `vagrant up`.
 
dcastellani@dcastellani-mbp ~/D/g/d/vagrant> vagrant ssh
 
[vagrant@localhost ~]$ ll -ah /vagrant/
total 0
drwxr-xr-x.  2 root root   6 Jun 20 13:25 .
dr-xr-xr-x. 18 root root 239 Jun 20 13:25 ..
 
[vagrant@localhost ~]$ ll -ah /sbin/mount*
-rwxr-xr-x. 1 root root  41K Nov  5  2016 /sbin/mount.cifs
-rwsr-xr-x. 1 root root 111K Mar  3 07:09 /sbin/mount.nfs
lrwxrwxrwx. 1 root root    9 Apr 21 23:15 /sbin/mount.nfs4 -> mount.nfs
-rwxr-xr-x. 1 root root  35K Mar  3 07:09 /sbin/mountstats
lrwxrwxrwx. 1 root root   49 Apr 21 23:17 /sbin/mount.vboxsf -> /opt/VBoxGuestAdditions-5.1.20/other/mount.vboxsf
 
[vagrant@localhost ~]$ ll -ah /opt/VBoxGuestAdditions-5.1.20/other/
ls: cannot access /opt/VBoxGuestAdditions-5.1.20/other/: No such file or directory
 
[vagrant@localhost ~]$ ll -ah /opt/VBoxGuestAdditions-5.1.20/lib/VBoxGuestAdditions/mount.*
-rwxr-xr-x. 1 root root 19K Apr 18 08:51 /opt/VBoxGuestAdditions-5.1.20/lib/VBoxGuestAdditions/mount.vboxsf

Work around for issue

[vagrant@localhost ~]$ sudo ln -sf /opt/VBoxGuestAdditions-5.1.20/lib/VBoxGuestAdditions/mount.vboxsf /sbin/mount.vboxsf
 
[vagrant@localhost ~]$ ll -ah /sbin/mount*
-rwxr-xr-x. 1 root root  41K Nov  5  2016 /sbin/mount.cifs
-rwsr-xr-x. 1 root root 111K Mar  3 07:09 /sbin/mount.nfs
lrwxrwxrwx. 1 root root    9 Apr 21 23:15 /sbin/mount.nfs4 -> mount.nfs
-rwxr-xr-x. 1 root root  35K Mar  3 07:09 /sbin/mountstats
lrwxrwxrwx. 1 root root   66 Jun 20 13:30 /sbin/mount.vboxsf -> /opt/VBoxGuestAdditions-5.1.20/lib/VBoxGuestAdditions/mount.vboxsf
 
[vagrant@localhost ~]$ exit
logout
Connection to 127.0.0.1 closed.
 
dcastellani@dcastellani-mbp ~/D/g/d/vagrant> vagrant reload
==> default: Attempting graceful shutdown of VM...
==> default: Checking if box 'geerlingguy/centos7' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
    default: /vagrant => /Users/dcastellani/Documents/git/dcastellani_infra/vagrant
 
dcastellani@dcastellani-mbp ~/D/g/d/vagrant> vagrant ssh
Last login: Tue Jun 20 13:26:34 2017 from 10.0.2.2
 
[vagrant@localhost ~]$ ll /vagrant/
total 4
-rw-r--r--. 1 vagrant vagrant 3023 Jun 19 21:00 Vagrantfile

Fix for issue

https://www.virtualbox.org/ticket/16670#comment:4

Looks like fix is to upgrade VBoxGuestAdditions within the box to 5.1.22 which you have already done it seems in geerlingguy/centos7 v 1.2.2 but have not released the version.

vagrantu up crashes with "vboxsf is not available" on Windows 10

I did updated everything to latest version.

OS: Windows 10 Enterprise 10.0.16299 (Build 16299)
Virtual Box: 5.2.12 r122591 (Qt5.6.2)
Vagrant: 2.1.2
Plugin: vagrant-vbguest (0.15.2)

Vagrantfile Sync Folder Config:
config.vm.synced_folder "vagrant_data", "/vagrant_data"

Output from vagrant up command (copying relevant part only):

==> default: Rsyncing folder: /cygdrive/c/Users/XXX/Documents/XXX/Vagrant/centos-7-ansible/ => /vagrant
==> default: Mounting shared folders...
    default: /vagrant_data => C:/Users/XXX/Documents/XXX/Vagrant/centos-7-ansible/vagrant_data
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

mount -t vboxsf -o uid=1000,gid=1000 vagrant_data /vagrant_data

The error output from the command was:

/sbin/mount.vboxsf: mounting failed with the error: No such device

Please suggest solution.

Trouble with Remote Connection Disconnect...

I've successfully ran vagrant boxes (specifically our old friend scotchbox) on my machine in the past, but with this specific one (using Virtualbox 5.1.26, Vagrant 1.9.7, Packer 1.0.3) I'm getting the following ad nauseum:

virtualbox: SSH address: 127.0.0.1:2222 virtualbox: SSH username: vagrant virtualbox: SSH auth method: private key virtualbox: Warning: Connection reset. Retrying... virtualbox: Warning: Remote connection disconnect. Retrying... virtualbox: Warning: Connection reset. Retrying... virtualbox: Warning: Remote connection disconnect. Retrying... virtualbox: Warning: Connection reset. Retrying... virtualbox: Warning: Remote connection disconnect. Retrying... virtualbox: Warning: Connection reset. Retrying...

Any thoughts? Has anyone else run into this?

Unable to vagrant up the new box

Following the README, I've created the new box at builds/virtualbox-centos7.box.

However, attempting to vagrant up fails with:

$ vagrant up virtualbox --provider=virtualbox
Bringing machine 'virtualbox' up with 'virtualbox' provider...
==> virtualbox: Box 'file://builds/virtualbox-centos7.box' could not be found. Attempting to find and install...
    virtualbox: Box Provider: virtualbox
    virtualbox: Box Version: >= 0
==> virtualbox: Box file was not detected as metadata. Adding it directly...
==> virtualbox: Adding box 'file://builds/virtualbox-centos7.box' (v0) for provider: virtualbox
    virtualbox: Unpacking necessary files from: file:///Users/jason/Projects/packer-centos-7/builds/virtualbox-centos7.box
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

Attempting to add the box directly to Vagrant gives this result:

$ vagrant box add virtualbox-centos7 builds/virtualbox-centos7.box
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'virtualbox-centos7' (v0) for provider:
    box: Unpacking necessary files from: file:///Users/jason/Projects/packer-centos-7/builds/virtualbox-centos7.box
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

No other clues are left in the failure output. This is on OS/X with latest versions.

Timeout issue of SSH

Do you happen to get following timeout issue? the packer build is hang at this step.

2017/02/10 23:37:13 ui: ==> vmware-iso: Waiting for SSH to become available...
2017/02/10 23:37:13 packer: 2017/02/10 23:37:13 Lookup up IP information...
==> vmware-iso: Waiting for SSH to become available...
2017/02/10 23:37:13 packer: 2017/02/10 23:37:13 DHCP leases path: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
2017/02/10 23:37:13 packer: 2017/02/10 23:37:13 IP lookup failed: IP not found for MAC 00:0c:29:78:59:7b in DHCP leases at /var/db/vmware/vmnet-dhcpd-vmnet8.leases
2017/02/10 23:37:13 packer: 2017/02/10 23:37:13 [DEBUG] Error getting SSH address: IP lookup failed: IP not found for MAC 00:0c:29:78:59:7b in DHCP leases at /var/db/vmware/vmnet-dhcpd-vmnet8.leases
2017/02/10 23:37:18 packer: 2017/02/10 23:37:18 Lookup up IP information...
2017/02/10 23:37:18 packer: 2017/02/10 23:37:18 DHCP leases path: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
2017/02/10 23:37:18 packer: 2017/02/10 23:37:18 IP lookup failed: IP not found for MAC 00:0c:29:78:59:7b in DHCP leases at /var/db/vmware/vmnet-dhcpd-vmnet8.leases
2017/02/10 23:37:18 packer: 2017/02/10 23:37:18 [DEBUG] Error getting SSH address: IP lookup failed: IP not found for MAC 00:0c:29:78:59:7b in DHCP leases at /var/db/vmware/vmnet-dhcpd-vmnet8.leases
2017/02/10 23:37:23 packer: 2017/02/10 23:37:23 Lookup up IP information...
2017/02/10 23:37:23 packer: 2017/02/10 23:37:23 DHCP leases path: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
2017/02/10 23:37:23 packer: 2017/02/10 23:37:23 Detected IP: 172.16.144.138
2017/02/10 23:37:24 packer: 2017/02/10 23:37:24 [DEBUG] TCP connection to SSH ip/port failed: dial tcp 172.16.144.138:22: getsockopt: connection refused
2017/02/10 23:37:29 packer: 2017/02/10 23:37:29 Lookup up IP information...
2017/02/10 23:37:29 packer: 2017/02/10 23:37:29 DHCP leases path: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
2017/02/10 23:37:29 packer: 2017/02/10 23:37:29 Detected IP: 172.16.144.138
2017/02/10 23:37:29 packer: 2017/02/10 23:37:29 [DEBUG] TCP connection to SSH ip/port failed: dial tcp 172.16.144.138:22: getsockopt: connection refused
2017/02/10 23:37:31 packer: 2017/02/10 23:37:31 handshake error: ssh: handshake failed: EOF
2017/02/10 23:37:31 packer: 2017/02/10 23:37:31 [DEBUG] SSH handshake err: ssh: handshake failed: EOF
2017/02/10 23:37:34 packer: 2017/02/10 23:37:34 Lookup up IP information...
2017/02/10 23:37:34 packer: 2017/02/10 23:37:34 DHCP leases path: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
2017/02/10 23:37:34 packer: 2017/02/10 23:37:34 Detected IP: 172.16.144.138
2017/02/10 23:37:34 packer: 2017/02/10 23:37:34 [DEBUG] TCP connection to SSH ip/port failed: dial tcp 172.16.144.138:22: getsockopt: connection refused
2017/02/10 23:37:38 packer: 2017/02/10 23:37:38 [INFO] Attempting SSH connection...
2017/02/10 23:37:38 packer: 2017/02/10 23:37:38 reconnecting to TCP connection for SSH
2017/02/10 23:37:38 packer: 2017/02/10 23:37:38 handshaking with SSH
2017/02/10 23:37:38 packer: 2017/02/10 23:37:38 handshake error: ssh: handshake failed: EOF
2017/02/10 23:37:38 packer: 2017/02/10 23:37:38 [DEBUG] SSH handshake err: ssh: handshake failed: EOF
2017/02/10 23:37:39 packer: 2017/02/10 23:37:39 Lookup up IP information...
2017/02/10 23:37:39 packer: 2017/02/10 23:37:39 DHCP leases path: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
2017/02/10 23:37:39 packer: 2017/02/10 23:37:39 Detected IP: 172.16.144.138
2017/02/10 23:37:39 packer: 2017/02/10 23:37:39 [DEBUG] TCP connection to SSH ip/port failed: dial tcp 172.16.144.138:22: getsockopt: connection refused
2017/02/10 23:37:44 packer: 2017/02/10 23:37:44 Lookup up IP information...
2017/02/10 23:37:44 packer: 2017/02/10 23:37:44 DHCP leases path: /var/db/vmware/vmnet-dhcpd-vmnet8.leases

Add support for VMware provider

See similar issue for Ubuntu 14.04 box: geerlingguy/packer-ubuntu-1404#3

Update for CentOS 7.4, push new box with VirtualBox 5.2.10 Guest Additions

See title... basically update all the things!

Warning: Authentication failure. Retrying...

After building this image I get these errors:

virtualbox: Warning: Remote connection disconnect. Retrying...
virtualbox: Warning: Connection reset. Retrying...
virtualbox: Warning: Remote connection disconnect. Retrying...
virtualbox: Warning: Connection reset. Retrying...

.....

virtualbox: Warning: Authentication failure. Retrying...
virtualbox: Warning: Authentication failure. Retrying...
virtualbox: Warning: Authentication failure. Retrying...
virtualbox: Warning: Authentication failure. Retrying...

....

**Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.**

ERROR! Unexpected Exception: (setuptools 0.9.8 (/usr/lib/python2.7/site-packages), Requirement.parse('setuptools>=11.3'))

When reaching step of provisioning Virtualbox centos7 image I get a failure. My guess is newer Ansible version requires a newer version of setuptools then is currently not included on centos7 image causing provisioning to fail. see below
`
==> virtualbox-iso: Provisioning with Ansible...
virtualbox-iso: Creating Ansible staging directory...
virtualbox-iso: Creating directory: /tmp/packer-provisioner-ansible-local
virtualbox-iso: Uploading main Playbook file...
virtualbox-iso: Uploading inventory file...
virtualbox-iso: Uploading role directories...
virtualbox-iso: Creating directory: /tmp/packer-provisioner-ansible-local/roles/geerlingguy.packer-rhel
virtualbox-iso: Creating directory: /tmp/packer-provisioner-ansible-local/roles/geerlingguy.nfs
virtualbox-iso: Executing Ansible: cd /tmp/packer-provisioner-ansible-local && ANSIBLE_FORCE_COLOR=1 PYTHONUNBUFFERED=1 ansible-playbook /tmp/packer-provisioner-ansible-local/main.yml -c local -i /tmp/packer-provisioner-ansible-local/packer-provisioner-ansible-local185464981
virtualbox-iso: ERROR! Unexpected Exception: (setuptools 0.9.8 (/usr/lib/python2.7/site-packages), Requirement.parse('setuptools>=11.3'))
virtualbox-iso: the full traceback was:
virtualbox-iso:
virtualbox-iso: Traceback (most recent call last):
virtualbox-iso: File "/usr/bin/ansible-playbook", line 73, in
virtualbox-iso: mycli = getattr(import("ansible.cli.%s" % sub, fromlist=[myclass]), myclass)
virtualbox-iso: File "/usr/lib/python2.7/site-packages/ansible/cli/playbook.py", line 30, in
virtualbox-iso: from ansible.executor.playbook_executor import PlaybookExecutor
virtualbox-iso: File "/usr/lib/python2.7/site-packages/ansible/executor/playbook_executor.py", line 27, in
virtualbox-iso: from ansible.executor.task_queue_manager import TaskQueueManager
virtualbox-iso: File "/usr/lib/python2.7/site-packages/ansible/executor/task_queue_manager.py", line 28, in
virtualbox-iso: from ansible.executor.play_iterator import PlayIterator
virtualbox-iso: File "/usr/lib/python2.7/site-packages/ansible/executor/play_iterator.py", line 29, in
virtualbox-iso: from ansible.playbook.block import Block
virtualbox-iso: File "/usr/lib/python2.7/site-packages/ansible/playbook/init.py", line 25, in
virtualbox-iso: from ansible.playbook.play import Play
virtualbox-iso: File "/usr/lib/python2.7/site-packages/ansible/playbook/play.py", line 27, in
virtualbox-iso: from ansible.playbook.base import Base
virtualbox-iso: File "/usr/lib/python2.7/site-packages/ansible/playbook/base.py", line 35, in
virtualbox-iso: from ansible.parsing.dataloader import DataLoader
virtualbox-iso: File "/usr/lib/python2.7/site-packages/ansible/parsing/dataloader.py", line 32, in
virtualbox-iso: from ansible.parsing.vault import VaultLib
virtualbox-iso: File "/usr/lib/python2.7/site-packages/ansible/parsing/vault/init.py", line 67, in
virtualbox-iso: from cryptography.hazmat.primitives.hashes import SHA256 as c_SHA256
virtualbox-iso: File "/usr/lib64/python2.7/site-packages/cryptography/hazmat/primitives/hashes.py", line 15, in
virtualbox-iso: from cryptography.hazmat.backends.interfaces import HashBackend
virtualbox-iso: File "/usr/lib64/python2.7/site-packages/cryptography/hazmat/backends/init.py", line 7, in
virtualbox-iso: import pkg_resources
virtualbox-iso: File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 3011, in
virtualbox-iso: parse_requirements(requires), Environment()
virtualbox-iso: File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 630, in resolve
virtualbox-iso: raise VersionConflict(dist,req) # XXX put more info here
virtualbox-iso: VersionConflict: (setuptools 0.9.8 (/usr/lib/python2.7/site-packages), Requirement.parse('setuptools>=11.3'))'

Docker build

This is actually in reference to Drupal VM but I thought I'd post about it in one of these box repositories instead. Seems like the more appropriate place. Also I havent read up on packer/docker/vagrant integrations at all, I just saw that it's possible to use docker with Vagrant.

Would it be a good idea to provide "supported" docker builds for these boxes as well? I'm imagining using those as bases for all your role tests on travis, as well as possibly even running Drupal VM within a container instead of a VM. Sounds pretty cool for local CI setups.

I'm not saying this would be provided out of the box in Drupal VMs case, but if we facilitate working boxes we can add a section to the docs about how to use containers through Vagrantfile.local.

I have no idea if this is even feasible or maintainable though... It just sounds awesome.

Add cifs-utils package

cifs-utils is needed for the machine to mount smb shares.

See: geerlingguy/drupal-vm#1147 (comment)

A source of Ansible packages for RHEL/CentOS will change soon

In order to align better with Red Hat processes, the Ansible team will be making some changes in how Ansible packages are distributed to the community.

For users of RHEL/CentOS/Scientific Linux version 7, the Ansible package will transition from the EPEL repository to the Extras channel. There will be no change for version 6 of RHEL/CentOS/Scientific Linux as Extras is not a part of version 6.

Source

vagrantu up crashes with "vboxsf is not available" on Windows 10

I am running into this issue when running vagrant reload, or vagrant halt + vagrant up.

vagrant destroy + vagrant up solves the issue until it is haltet or reloaded.

Environment:
geerlingguy/centos7 version 1.7
virtualbox 5.1.12 r112440
windows 10

Any idea what is causing this?

It was working previously on the same pc and I'm not really sure what introduced this error; virtualbox, vagrant or the box itself.

Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

The error output from the command was:

/sbin/mount.vboxsf: mounting failed with the error: No such device