boxcutter / centos Goto Github PK

View Code? Open in Web Editor NEW

423.0 423.0 199.0 427 KB

Virtual machine templates for CentOS written in legacy JSON

License: Apache License 2.0

Makefile 7.26% Shell 79.43% Ruby 13.31%

centos's People

Contributors

Stargazers

Watchers

Forkers

pro-vagrant kontrafiktion tai-ga lingxuan630 rickard-von-essen webdizz brentley jongillies fydon temna-net blairham kunihiko-fujise epu leonkyneur terrycorley nc6 vvv briancline jackkb rasputnik hazymoon paulustm grafjo chenpiao erikh gabelbombe cmacdonald-au nazy tom--bo kosaki oldcrowew bgdevlab idi-ops jblaine witjoh satom9to5 zeus911 patrick-hill awisu2 mahata paulojeronimo daxgames chnzjm bcorner13 4sp1r3 songwenbin mrgarymartin htrc brendanmcq leriksen newamsterdamlabs cccsv cognivator bibnets henrycv mktktmr spivegin scottatron vpassapera benpriestman chrisduong arechste im-afebruary oyang grange74 jqnik ryanfrench mrsecure sumsung007 ike-jp sazpaimon luiz158 abrooke-forks daratmonkey mklemm2 alst74 mrjcleaver meenachisundaram leestubbs digitalmichael martinjotpunkt sci-burns jakirkham alchen99 dddpaul anxiaowu kkirsche wildone rbramwell andrewstarling n3gster robertchen thatsk podlom june-yang randyporter salt-lick jason-azze smougenot tsuttsu305

centos's Issues

Folder of custom scripts

Wouldn't it be better if custom script was a folder instead of a single file? That way things could be modularized. They could be run in alpha sort order, etc.

I'd suppose this should be a generic Boxcutter issue tracker issue, but I don't see one...

centos7 vm can not ping 10.0.2.2 failed.

I run the packer build -only=virtualbox-iso centos.json in my windows10.
It was stopped at "==> virtualbox-iso: Waiting for SSH to become available..." command line.
I checked the log in virtualbox, it show "Failed connect 10.0.2.2:8853".
But I can ping the ip successfully in another virtualbox（created by manual）。

experimental: reduce number of templates (centos70*)?

I did an experiment, reducing the number of templates (thereby making the templates and scripts somewhat more complicated): https://github.com/kontrafiktion/centos/tree/redux70

the centos70, centos70-desktop, and centos70-docker templates are mostly identical.
They only differ in some variable values (disk_size, mem_size, vm_name), but the builders themselves are nearly identical.
All variants execute the same shell scripts which now check for an environment variable (INSTALL_DOCKER, INSTALL_DESKTOP).
The only real difference left ist the vagrant template: it is only used in the desktop variant, but that could be eliminated as well by using a much simpler template for the other two variants.

I am not sure, if this simplifies or complicates things, but I never like copy and paste.

I did not delete the templates and did not yet adapt the makefile, just wanted to get some feedback

Missing vmware-tools in v2.0.3(vmware_desktop,minimal)

Hello and many thanks for this great work.
In v2.0.3 loading the HGFS kernel module failed and the folder /lib/vmware-tools is missing.
Best regards,Uli
PS: installed via 'vagrant init boxcutter/centos71; vagrant up --provider vmware_desktop'

sudo: sorry, you must have a tty to run sudo

After running "make virtualbox/centos66" and adding the box to vagrant, a "vagrant up" fails with "sudo: sorry, you must have a tty to run sudo" when executing "mkdir -p /vagrant".

The ks6.cfg file indicates that "requiretty" should be commented out of the /etc/sudoers file, but it does not appear that this worked correctly (as it is not commented out).

The output of a "ls -la /etc/sud_" is:
[vagrant@localhost ~]$ ls -la /etc/sud_
-rw-r-----. 1 root root 1786 Sep 25 2012 /etc/sudo.conf
-r--r-----. 1 root root 4002 Mar 1 2012 /etc/sudoers
-rw-r--r--. 1 root root 77 May 26 15:05 /etc/sudoers?
-r--r-----. 1 root root 4002 May 26 15:05 /etc/sudoers.orig?
-rw-r-----. 1 root root 3181 Jul 31 2014 /etc/sudo-ldap.conf

Notice the trailing "?", where the ks6.cfg file indicates the original "sudoers" file should be copied to "sudoers.orig". Lastly, the "sudoers" file contains only the line:

Defaults env_keep += "HTTP_PROXY HTTPS_PROXY FTP_PROXY RSYNC_PROXY NO_PROXY"

I am running "make virtualbox/centos66" under Cygwin on Windows 7.

Any help is greatly appreciated.

Steve Ardis

How to change the user and password?

Hey,

How does one change it from being vagrant vagrant? ...

"ssh_password"
"ssh_username"

doesn't actually work

/etc/machine-id should be emptied not removed

[https://bugzilla.redhat.com/show_bug.cgi?id=1379800]

In script/cleanup.sh it should then say:

echo "==> Clear out machine id"
rm -f /etc/machine-id
touch /etc/machine-id

Uniform name for repo

I suggest unifor names for all repos:

Virtual machine templates for XXXX

(in GitHub interface).

update request for CentOS 7.2 images on AtlasCorp

Hello, I appreciate everyone's work on all these boxes. I am currently using the CentOS 7.2 vagrant image here (https://atlas.hashicorp.com/boxcutter/boxes/centos72/) and am noticing that each time I run vagrant up VirtualBox recompiles the Guest Additions to 5.0.16. I'm hoping whoever controls these images can update them to the latest VBox Guest Additions and run a yum update. Thanks in advance!

CentOS 6.6: don't respect selinux setting in kickstart file

For great info see: chef/bento#306

I'll try to do a PR soon.

No guest IP was given to the Vagrant core NFS helper.

If i try to boot a already installed vagrant box i get the following message:

No guest IP was given to the Vagrant core NFS helper. This is an
internal error that should be reported as a bug.

I get this error after upgrading all packages (using ansible)

name: upgrade all packages
yum: name=* state=latest

[Feature] Ansible

I just noticed that you provide the option to install Ansible as a provisioner for the Unbuntu boxes. Would it be possible for you to add Ansible for the Centos boxes as well?

Custom "internal" software repos?

We are thinking about making a feature to enable custom "internal" software repositories. Some environments are "air gapped" (as in no Internet access), and as such, the default software repositories are not useful. I am trying to decide whether it would be smarter to use the "file" provisioner to just dump the contents of a directory into yum.repos.d or whether it should be some sort of scripted interface.

I am just throwing this out there to see if anyone else has already done this, and/or if anyone has any ideas about what would be good or bad?

Tommy

RHEL?

Hi - are these templates also workable for Red Hat Enterprise Linux?

Thanks, Martin

Question - Building All Images

Hey there,

What is the best, and most efficient way to build all of the images?

Thanks,

Brendan

Wrong interface in Centos72 box gets the vagrant dhcp configuration

This may be a configuration problem on my end, but whenever I try to vagrant up a boxcutter/centos72 box with more than one interface, I get this output:

==> server01: Importing base box 'boxcutter/centos72'...
==> server01: Matching MAC address for NAT networking...
==> server01: Checking if box 'boxcutter/centos72' is up to date...
==> server01: Setting the name of the VM: 1_server01
==> server01: Fixed port collision for 22 => 2222. Now on port 2201.
==> server01: Clearing any previously set network interfaces...
==> server01: Preparing network interfaces based on configuration...
    server01: Adapter 1: nat
    server01: Adapter 2: intnet
    server01: Adapter 3: intnet
    server01: Adapter 4: intnet
==> server01: Forwarding ports...
    server01: 22 (guest) => 2201 (host) (adapter 1)
==> server01: Running 'pre-boot' VM customizations...
==> server01: Booting VM...
==> server01: Waiting for machine to boot. This may take a few minutes...
    server01: SSH address: 127.0.0.1:2201
    server01: SSH username: vagrant
    server01: SSH auth method: private key
    server01: Warning: Remote connection disconnect. Retrying...
    server01: Warning: Remote connection disconnect. Retrying...
    server01: Warning: Remote connection disconnect. 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.

My vagrant config is as below:

config.vm.define "server01" do |device|
    device.vm.hostname = "server01"
    device.vm.box = "boxcutter/centos72"

    device.vm.provider "virtualbox" do |v|
      v.name = "#{wbid}_server01"
      v.customize ["modifyvm", :id, '--audiocontroller', 'AC97', '--audio', 'Null']
      v.memory = 512
    end
    device.vm.synced_folder ".", "/vagrant", disabled: true

      # NETWORK INTERFACES
      device.vm.network "private_network", virtualbox__intnet: "#{wbid}_net42", auto_config: false , :mac => "a00000000031"

      device.vm.network "private_network", virtualbox__intnet: "#{wbid}_net2", auto_config: false , :mac => "443839000003"

      device.vm.network "private_network", virtualbox__intnet: "#{wbid}_net13", auto_config: false , :mac => "443839000017"


    device.vm.provider "virtualbox" do |vbox|
      vbox.customize ['modifyvm', :id, '--nicpromisc2', 'allow-all']
      vbox.customize ['modifyvm', :id, '--nicpromisc3', 'allow-all']
      vbox.customize ['modifyvm', :id, '--nicpromisc4', 'allow-all']
   end
  end

When I go in through the console to investigate what's going on, it looks like DHCP is configured by default on the LAST interface Adapter 4 instead of the first Adapter 1 (the default Vagrant NAT interface). The only script in /etc/sysconfig/network-scripts is the device of Adapter 4, even though you can see it's explicitly set as auto-config=False. If I manually activate DHCP on Adapter 1 through the console, everything (such as Vagrant ssh) starts working as would expect.

Does anyone here have any insight?

cleanup.sh is broken

Hello,

We've been using this repo as a template for building CentOS VMs. When building a CentOS minimal install against ESXi hosts the vmware customizations are never applied. This is because the vmware tools require Perl to remain installed. In our testing of removing Perl from this line:
https://github.com/boxcutter/centos/blob/master/script/cleanup.sh#L73

Is not enough to fix the issues with customizations not applying. We have not yet determined which packages are required, but I'm fairly confident at a bare minimum kernel-devel, kernel-headers, perl and gcc need to remain installed.

Hopefully this helps save time for any other users that run into this issue.

Thanks!
ZC

Supporting additional builders?

Hi.

I've been doing qemu/kvm box templates for myself and was wondering if pull requests relating to supporting qemu builder would be welcome (or not) here? I'll be probably covering centos, ubuntu and windows since I need all of those myself.

README.md refers to wrong CentOS version

Please update all references in the docs to centos71 to centos72

Ansible-friendly image?

To be fair I've no idea if you use Ansible, but I can't provision
with it on this VM because it needs libselinux-python to work against
any linux with 'permissive' or higher settings.
(this previously worked on your images, was broken by
149a609
).

I'm in a bit of a bind since I can't set yum to use a proxy until ansible works,
which requires the rpm be downloaded... catch 22.

Would you consider adding this to your images?

VMware guest customizations fail due to lack of perl

Hi all, not sure what (if anything) can be done due to the circumstances, but here goes:

I've been using the vmware-desktop boxes, extracting them, and importing them into vSphere for use with Terraform. The Ubuntu boxes work correctly, but I tried doing the same with CentOS but it failed the guest customization. The logs show it failed because perl is required but is removed by Packer after the guest tools are installed. I booted up the template, installed perl, and guest customizations are now succeeding.

I guess since these boxes are created for use in Vagrant (and by extension specifically the vmware-desktop driver) making them compatible with ESXi is out of scope, but just thought I'd bring this up and get some feedback from you.

Unable to use custom ssh username/password while building the box?

Hi, I have set the SSH_USERNAME, SSH_PASSWORD varables in Makefile.local, but it looks like this is failing. I can see that the variables are being taken into consideration -

packer build -only=virtualbox-iso -var 'cm=chef' -var 'headless=true' -var 'update=true' -var 'version=1.0.13' -var 'ssh_username=stsdev' -var 'ssh_password=stsdev' -var 'install_vagrant_key=false' -var 'iso_path=/home/dnataraj/Downloads/' -var 'cm_version=latest' centos70-sts.json

And then make fails with the error -

==> virtualbox-iso: Waiting 10s for boot...
==> virtualbox-iso: Typing the boot command...
==> virtualbox-iso: Waiting for SSH to become available...
==> virtualbox-iso: Error waiting for SSH: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain
==> virtualbox-iso: Unregistering and deleting virtual machine...
==> virtualbox-iso: Deleting output directory...
Build 'virtualbox-iso' errored: Build was halted.

Have I missed anything obvious? Thanks.

CentOS 7 iso download fails

The rebuild of CentOS 7 fails:

    virtualbox-iso: Error downloading: Error making HTTP GET request: 404 Not Found
==> virtualbox-iso: ISO download failed.
Build 'virtualbox-iso' errored: ISO download failed.

I guess a later update than 7.6.1810 is now needed

ISO path overrides no longer working

$ cat Makefile.local
CENTOS66_X86_64 = /Volumes/Drobo/annex/iso/CentOS-6.6-x86_64-bin-DVD1.iso

$ make virtualbox/centos66
rm -rf output-virtualbox-iso
mkdir -p box/virtualbox
packer build -only=virtualbox-iso -var 'cm=nocm' -var 'headless=' -var 'update=' -var 'version=1.0.13' -var 'ssh_username=vagrant' -var 'ssh_password=vagrant' -var 'install_vagrant_key=true' -var 'iso_path=iso' centos66.json
virtualbox-iso output will be in this color.

==> virtualbox-iso: Downloading or copying Guest additions
    virtualbox-iso: Downloading or copying: file:///Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso
==> virtualbox-iso: Downloading or copying ISO
    virtualbox-iso: Downloading or copying: file:///iso/CentOS-6.6-x86_64-bin-DVD1.iso
    virtualbox-iso: Error downloading: open /iso/CentOS-6.6-x86_64-bin-DVD1.iso: no such file or directory
    virtualbox-iso: Downloading or copying: http://mirrors.kernel.org/centos/6.6/isos/x86_64/CentOS-6.6-x86_64-bin-DVD1.iso

The Makefile is setting ISO_PATH to the following:

ISO_PATH ?= iso

It appears that since the inclusion of this environment variable, there was no glue written to tie the ISO overrides to the ISO_PATH

box-cutter/centos511 is in a 'gurumeditation' state and doesn't work.

Tested on two different machines with:

macOS Sierra 10.12.1 and 10.12
VirtualBox 5.1.8

Any other box runs fine. One of the machines was running an old version of box-cutter/centos511 and it broke when I did a box update.

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'box-cutter/centos511'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'box-cutter/centos511' is up to date...
==> default: Setting the name of the VM: vagrant_default_1478238840903_98242
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2200 (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:2200
    default: SSH username: vagrant
    default: SSH auth method: private key
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'gurumeditation' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.

My vagrantfile is super simple:

Vagrant.configure('2') do |config|
  config.vm.box = 'box-cutter/centos511'
end

Any other box I run including boxcutter/ubuntu runs fine.

version 2.0.12 fails in combination with vagrant docker provisioner

Using

Vagrant.configure(2) do |config|
  config.vm.box = "boxcutter/centos72"
  config.vm.box_version = "2.0.12"
  config.vm.provision "docker" do |d|
  end
end

and running

vagrant up --provider virtualbox
vagrant halt
vagrant up --provider virtualbox

will fail with

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'boxcutter/centos72' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2200 (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:2200
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
GuestAdditions seems to be installed (5.0.14) correctly, but not running.
Usage: service < option > | --status-all | [ service_name [ command | --full-restart ] ]
bash: line 3: vboxadd: command not found
Removing existing VirtualBox non-DKMS kernel modules[  OK  ]
Building the VirtualBox Guest Additions kernel modules
The gcc utility was not found. If the following module compilation fails then
this could be the reason and you should try installing it.

The headers for the current running kernel were not found. If the following
module compilation fails then this could be the reason.
The missing package can be probably installed with
yum install kernel-devel-3.10.0-327.13.1.el7.x86_64

Building the main Guest Additions module[FAILED]
(Look at /var/log/vboxadd-install.log to find out what went wrong)
Doing non-kernel setup of the Guest Additions[  OK  ]
Restarting VM to apply changes...
==> default: Attempting graceful shutdown of VM...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2200
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
    default: /vagrant => /home/jarl/tmp/centos72
Failed to mount folders in Linux guest. This is usually because
the "vboxsf" file system is not available. Please verify that
the guest additions are properly installed in the guest and
can work properly. The command attempted was:

mount -t vboxsf -o uid=`id -u vagrant`,gid=`getent group vagrant | cut -d: -f3` vagrant /vagrant
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` vagrant /vagrant

The error output from the last command was:

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

I have investigated a bit with vagrant --debug and the problem is caused by the docker provisioning is running a yum -q -y update which installs a new kernel (without kernel headers).

CentOS 5 EOL - 31 March

'Vagrant up' fails while restarting network service under parallels with boxcutter/centos7, version 17.0904.1

Assuming:

vagrant (version 2.0.0, 1.9.4, and 1.8.6 all exhibit the same behavior)
parallels 12.2.1
boxcutter/centos7 box 17.0904.1
all running under macOS 10.12.6 (Sierra)

Attempting to run 'vagrant up' on a minimal vagrant box as defined in the attached Vagrantfile.txt fails in the following manner:

$ vagrant --version
Vagrant 2.0.0

$ prlctl --version
prlctl version 12.2.1 (41615)

$ vagrant box list
boxcutter/centos7   (parallels, 17.0904.1)

$ vagrant --provider=parallels up
Bringing machine 'centos7' up with 'parallels' provider...
==> centos7: Registering VM image from the base box 'boxcutter/centos7'...
==> centos7: Cloning new virtual machine...
==> centos7: Unregistering the box VM image...
==> centos7: Setting the default configuration for VM...
==> centos7: Checking if box 'boxcutter/centos7' is up to date...
==> centos7: Setting the name of the VM: tmp_centos7_1504912986672_60599
==> centos7: Preparing network interfaces based on configuration...
    centos7: Adapter 0: shared
==> centos7: Clearing any previously set network interfaces...
==> centos7: Booting VM...
==> centos7: Waiting for machine to boot. This may take a few minutes...
    centos7: SSH address: 10.211.55.12:22
    centos7: SSH username: vagrant
    centos7: SSH auth method: private key
    centos7: Warning: Connection refused. Retrying...
    centos7:
    centos7: Vagrant insecure key detected. Vagrant will automatically replace
    centos7: this with a newly generated keypair for better security.
    centos7:
    centos7: Inserting generated public key within guest...
    centos7: Removing insecure key from the guest if it's present...
    centos7: Key inserted! Disconnecting and reconnecting using new SSH key...
==> centos7: Machine booted and ready!
==> centos7: Checking for Parallels Tools installed on the VM...
==> centos7: Parallels Tools installed on this VM are outdated! In most cases
==> centos7: this is fine but in rare cases it can cause things such as shared
==> centos7: folders to not work properly. If you see shared folder errors,
==> centos7: please update Parallels Tools within the virtual machine and
==> centos7: reload your VM.
==> centos7: Setting hostname...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

# Update sysconfig
sed -i 's/\(HOSTNAME=\).*/\1centos7.vagrant.local/' /etc/sysconfig/network

# Update DNS
sed -i 's/\(DHCP_HOSTNAME=\).*/\1"centos7"/' /etc/sysconfig/network-scripts/ifcfg-*

# Set the hostname - use hostnamectl if available
echo 'centos7.vagrant.local' > /etc/hostname
if command -v hostnamectl; then
  hostnamectl set-hostname --static 'centos7.vagrant.local'
  hostnamectl set-hostname --transient 'centos7.vagrant.local'
else
  hostname -F /etc/hostname
fi

# Prepend ourselves to /etc/hosts
grep -w 'centos7.vagrant.local' /etc/hosts || {
  sed -i'' '1i 127.0.0.1\tcentos7.vagrant.local\tcentos7' /etc/hosts
}

# Restart network
service network restart


Stdout from the command:

/bin/hostnamectl
Restarting network (via systemctl):  [FAILED]


Stderr from the command:

Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.

This same Vagrantfile works as expected with the pre-migration boxcutter/centos73 version 2.0.21 box.

Output of 'systemctl status network.service' and 'journalctl --all' on the failing box are attached:
journalctl-output.txt
systemctl-output.txt

Any idea what might be going on here? I tried with multiple versions of vagrant, and a coworker was also able to reproduce my results, so I believe it's an issue with this version of the centos7 box.

Vagrant boxes not available on Vagrant cloud

Building a new vagrant box fails. Example Vagrantfile:

Vagrant.configure(2) do |config|

  config.vm.box = "boxcutter/centos7"
  config.vm.box_version = "17.0915.1"
end

It seems like all vagrant boxes are gone from vagrant cloud:
https://app.vagrantup.com/boxcutter

Please provide CentOS 8 variant

Now that CentOS 8 is out, it would be great to have it supported.

Thanx in advance.

Apply a static IP address

Hi,
I want to apply a static IP address to a box derived from this one.

Is a good way to do this using custom-script.sh? I'm leery of changing ks.cfg bootproto to static because I believe packer needs the VM to send a DHCP request so they know where each other are.

I appreciate I could post-process the my vmware-iso with vmware-vmx to add the script... I was trying to avoid a multi-step process.

Thanks,
Martin.

Makefile.local settings being ignored

Somewhere between 1.0.14 and 2.0.8 the Makefile.local overrides started being ignored as a result of refactoring the Makefile to invoke bin/box/build. However the README.md still documents it.
See example below:

centos$ cat Makefile.local 
CM = puppet
centos$ make -n build
bin/box build centos510-i386.json
bin/box build centos510.json
bin/box build centos511-i386.json
bin/box build centos511.json
bin/box build centos64-desktop.json
bin/box build centos64-i386.json
bin/box build centos64.json
bin/box build centos65-desktop.json
bin/box build centos65-docker.json
bin/box build centos65-i386.json
bin/box build centos65.json
bin/box build centos66-desktop.json
bin/box build centos66-docker.json
bin/box build centos66-i386.json
bin/box build centos66.json
bin/box build centos67-desktop.json
bin/box build centos67-docker.json
bin/box build centos67-i386.json
bin/box build centos67.json
bin/box build centos70-desktop.json
bin/box build centos70-docker.json
bin/box build centos70.json
bin/box build centos71-desktop.json
bin/box build centos71-docker.json
bin/box build centos71.json

The -var 'cm=puppet' option is not being based to packer.

Also the ability to use build one distro and provider only (had been make virtualbox/centos71) seems to have been dropped.

Workaround is to just use packer directly:

packer build -only=virtualbox-iso -var-file=centos71.json -var "version=`cat VERSION`" -var "cm=puppet" -var "update=true" centos.json

Unable to load HGFS driver while running under VMware workstation

Running this using vagrant (boxcutter/centos70 from atlas) under VMware workstation I get the following error:

Bringing machine 'testvm' up with 'vmware_workstation' provider...
==> testvm: Cloning VMware VM: 'boxcutter/centos70'. This can take some time...
==> testvm: Checking if box 'boxcutter/centos70' is up to date...
==> testvm: Verifying vmnet devices are healthy...
==> testvm: Preparing network adapters...
==> testvm: Starting the VMware VM...
==> testvm: Waiting for machine to boot. This may take a few minutes...
    testvm: SSH address: 192.168.33.219:22
    testvm: SSH username: vagrant
    testvm: SSH auth method: private key
    testvm:
    testvm: Vagrant insecure key detected. Vagrant will automatically replace
    testvm: this with a newly generated keypair for better security.
    testvm:
    testvm: Inserting generated public key within guest...
    testvm: Removing insecure key from the guest if its present...
    testvm: Key inserted! Disconnecting and reconnecting using new SSH key...
==> testvm: Machine booted and ready!
==> testvm: Forwarding ports...
    testvm: -- 80 => 8080
    testvm: -- 22 => 2222
==> testvm: Setting hostname...
==> testvm: Configuring network adapters within the VM...
==> testvm: Waiting for HGFS kernel module to load...
The HGFS kernel module was not found on the running virtual machine.
This must be installed for shared folders to work properly. Please
install the VMware tools within the guest and try again. Note that
the VMware tools installation will succeed even if HGFS fails
to properly install. Carefully read the output of the VMware tools
installation to verify the HGFS kernel modules were installed properly.

boxcutter release v2.0.16 does not have parallel tools installed

The current boxcutter release (v2.0.16) on atlas does not appear to have parallel tools installed:

==> centos72: Machine booted and ready!
==> centos72: Checking for Parallels Tools installed on the VM...
==> centos72: Parallels Tools were not detected on this VM! They are required
==> centos72: for shared folders, time sync and more. If shared folders are not
==> centos72: working on this machine, please install Parallels Tools within the
==> centos72: virtual machine and reload your VM.

SELinux should be permissive

SELinux should be permissive at the very least. This allows for quicker enablement with no need to relabel the filesystem to enable it again, and will still generate logs of policy violations to aid troubleshooting.

Squid is failed to start on centos 6.7

hello... i'm sorry... i have installed centos 6.7. and i want to build a proxy server using squid. but when i use command "service squid start/ restart" system said FAILED. i haven't changed the configuration. thank you for your attention.

Centos 6.8 kernel update, please publish new boxes

Please publish a new versions for Centos 6.8

It looks like kernel has been updated

[vagrant@localhost ~]$ yum list kernel
Modules complémentaires chargés : fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.quelquesmots.fr
 * extras: mirror.in2p3.fr
 * updates: ftp.rezopole.net
Paquets installés
kernel.x86_64                 2.6.32-642.el6                     @anaconda-CentOS-201605220104.x86_64/6.8
Paquets disponibles
kernel.x86_64                 2.6.32-696.1.1.el6                 updates

On Vagrant box : 'boxcutter/centos68' (v2.0.21) for 'virtualbox'

vagrant-vbguest plugin failed

vagrant-vbguest couldn't complete to install GuestAdditions for boxcutter/centos66 2.0.7.

Vagrant 1.7.4
VirstulBox 5.0.10
vagrant-vbguest 0.11.0
boxcutter/centos66 2.0.7

$ vagrant up --no-provision
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'boxcutter/centos66'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'boxcutter/centos66' is up to date...
==> default: Setting the name of the VM: xxxxxxxxxxxxxxxxxxxx_default_1447248730506_89208
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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: 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!
GuestAdditions versions on your host (5.0.10) and guest (5.0.8) do not match.
Loaded plugins: fastestmirror
Setting up Install Process
Determining fastest mirrors
 * base: ftp.iij.ad.jp
 * extras: ftp.iij.ad.jp
 * updates: ftp.iij.ad.jp
No package kernel-devel-2.6.32-504.el6.x86_64 available.
Package 1:make-3.81-20.el6.x86_64 already installed and latest version
Package bzip2-1.0.5-7.el6_0.x86_64 already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package gcc.x86_64 0:4.4.7-16.el6 will be installed
--> Processing Dependency: libgomp = 4.4.7-16.el6 for package: gcc-4.4.7-16.el6.x86_64
--> Processing Dependency: cpp = 4.4.7-16.el6 for package: gcc-4.4.7-16.el6.x86_64
--> Processing Dependency: libgcc >= 4.4.7-16.el6 for package: gcc-4.4.7-16.el6.x86_64
--> Processing Dependency: glibc-devel >= 2.2.90-12 for package: gcc-4.4.7-16.el6.x86_64
---> Package perl.x86_64 4:5.10.1-141.el6_7.1 will be installed
--> Processing Dependency: perl-libs = 4:5.10.1-141.el6_7.1 for package: 4:perl-5.10.1-141.el6_7.1.x86_64
--> Processing Dependency: perl-libs for package: 4:perl-5.10.1-141.el6_7.1.x86_64
--> Processing Dependency: perl(version) for package: 4:perl-5.10.1-141.el6_7.1.x86_64
--> Processing Dependency: perl(Pod::Simple) for package: 4:perl-5.10.1-141.el6_7.1.x86_64
--> Processing Dependency: perl(Module::Pluggable) for package: 4:perl-5.10.1-141.el6_7.1.x86_64
--> Processing Dependency: libperl.so()(64bit) for package: 4:perl-5.10.1-141.el6_7.1.x86_64
--> Running transaction check
---> Package cpp.x86_64 0:4.4.7-16.el6 will be installed
--> Processing Dependency: libmpfr.so.1()(64bit) for package: cpp-4.4.7-16.el6.x86_64
---> Package glibc-devel.x86_64 0:2.12-1.166.el6_7.3 will be installed
--> Processing Dependency: glibc-headers = 2.12-1.166.el6_7.3 for package: glibc-devel-2.12-1.166.el6_7.3.x86_64
--> Processing Dependency: glibc = 2.12-1.166.el6_7.3 for package: glibc-devel-2.12-1.166.el6_7.3.x86_64
--> Processing Dependency: glibc-headers for package: glibc-devel-2.12-1.166.el6_7.3.x86_64
---> Package libgcc.x86_64 0:4.4.7-11.el6 will be updated
---> Package libgcc.x86_64 0:4.4.7-16.el6 will be an update
---> Package libgomp.x86_64 0:4.4.7-11.el6 will be updated
---> Package libgomp.x86_64 0:4.4.7-16.el6 will be an update
---> Package perl-Module-Pluggable.x86_64 1:3.90-141.el6_7.1 will be installed
---> Package perl-Pod-Simple.x86_64 1:3.13-141.el6_7.1 will be installed
--> Processing Dependency: perl(Pod::Escapes) >= 1.04 for package: 1:perl-Pod-Simple-3.13-141.el6_7.1.x86_64
---> Package perl-libs.x86_64 4:5.10.1-141.el6_7.1 will be installed
---> Package perl-version.x86_64 3:0.77-141.el6_7.1 will be installed
--> Running transaction check
---> Package glibc.x86_64 0:2.12-1.149.el6 will be updated
--> Processing Dependency: glibc = 2.12-1.149.el6 for package: glibc-common-2.12-1.149.el6.x86_64
---> Package glibc.x86_64 0:2.12-1.166.el6_7.3 will be an update
---> Package glibc-headers.x86_64 0:2.12-1.166.el6_7.3 will be installed
--> Processing Dependency: kernel-headers >= 2.2.1 for package: glibc-headers-2.12-1.166.el6_7.3.x86_64
--> Processing Dependency: kernel-headers for package: glibc-headers-2.12-1.166.el6_7.3.x86_64
---> Package mpfr.x86_64 0:2.4.1-6.el6 will be installed
---> Package perl-Pod-Escapes.x86_64 1:1.04-141.el6_7.1 will be installed
--> Running transaction check
---> Package glibc-common.x86_64 0:2.12-1.149.el6 will be updated
---> Package glibc-common.x86_64 0:2.12-1.166.el6_7.3 will be an update
---> Package kernel-headers.x86_64 0:2.6.32-573.8.1.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package                  Arch      Version                    Repository  Size
================================================================================
Installing:
 gcc                      x86_64    4.4.7-16.el6               base        10 M
 perl                     x86_64    4:5.10.1-141.el6_7.1       updates     10 M
Installing for dependencies:
 cpp                      x86_64    4.4.7-16.el6               base       3.7 M
 glibc-devel              x86_64    2.12-1.166.el6_7.3         updates    986 k
 glibc-headers            x86_64    2.12-1.166.el6_7.3         updates    615 k
 kernel-headers           x86_64    2.6.32-573.8.1.el6         updates    3.9 M
 mpfr                     x86_64    2.4.1-6.el6                base       157 k
 perl-Module-Pluggable    x86_64    1:3.90-141.el6_7.1         updates     40 k
 perl-Pod-Escapes         x86_64    1:1.04-141.el6_7.1         updates     33 k
 perl-Pod-Simple          x86_64    1:3.13-141.el6_7.1         updates    213 k
 perl-libs                x86_64    4:5.10.1-141.el6_7.1       updates    579 k
 perl-version             x86_64    3:0.77-141.el6_7.1         updates     52 k
Updating for dependencies:
 glibc                    x86_64    2.12-1.166.el6_7.3         updates    3.8 M
 glibc-common             x86_64    2.12-1.166.el6_7.3         updates     14 M
 libgcc                   x86_64    4.4.7-16.el6               base       103 k
 libgomp                  x86_64    4.4.7-16.el6               base       134 k

Transaction Summary
================================================================================
Install      12 Package(s)
Upgrade       4 Package(s)

Total download size: 49 M
Downloading Packages:
--------------------------------------------------------------------------------
Total                                           1.4 MB/s |  49 MB     00:34     
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID c105b9de: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
Importing GPG key 0xC105B9DE:
 Userid : CentOS-6 Key (CentOS 6 Official Signing Key) <[email protected]>
 Package: centos-release-6-6.el6.centos.12.2.x86_64 (@anaconda-CentOS-201410241409.x86_64/6.6)
 From   : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Warning: RPMDB altered outside of yum.
  Updating   : libgcc-4.4.7-16.el6.x86_64                                  1/20 
  Updating   : glibc-common-2.12-1.166.el6_7.3.x86_64                      2/20 
  Updating   : glibc-2.12-1.166.el6_7.3.x86_64                             3/20 
  Updating   : libgomp-4.4.7-16.el6.x86_64                                 4/20 
  Installing : mpfr-2.4.1-6.el6.x86_64                                     5/20 
  Installing : cpp-4.4.7-16.el6.x86_64                                     6/20 
  Installing : 1:perl-Pod-Escapes-1.04-141.el6_7.1.x86_64                  7/20 
  Installing : 1:perl-Module-Pluggable-3.90-141.el6_7.1.x86_64             8/20 
  Installing : 3:perl-version-0.77-141.el6_7.1.x86_64                      9/20 
  Installing : 4:perl-libs-5.10.1-141.el6_7.1.x86_64                      10/20 
  Installing : 1:perl-Pod-Simple-3.13-141.el6_7.1.x86_64                  11/20 
  Installing : 4:perl-5.10.1-141.el6_7.1.x86_64                           12/20 
  Installing : kernel-headers-2.6.32-573.8.1.el6.x86_64                   13/20 
  Installing : glibc-headers-2.12-1.166.el6_7.3.x86_64                    14/20 
  Installing : glibc-devel-2.12-1.166.el6_7.3.x86_64                      15/20 
  Installing : gcc-4.4.7-16.el6.x86_64                                    16/20 
  Cleanup    : libgomp-4.4.7-11.el6.x86_64                                17/20 
  Cleanup    : glibc-common-2.12-1.149.el6.x86_64                         18/20 
  Cleanup    : glibc-2.12-1.149.el6.x86_64                                19/20 
  Cleanup    : libgcc-4.4.7-11.el6.x86_64                                 20/20 
  Verifying  : glibc-devel-2.12-1.166.el6_7.3.x86_64                       1/20 
  Verifying  : libgomp-4.4.7-16.el6.x86_64                                 2/20 
  Verifying  : 1:perl-Pod-Simple-3.13-141.el6_7.1.x86_64                   3/20 
  Verifying  : 1:perl-Pod-Escapes-1.04-141.el6_7.1.x86_64                  4/20 
  Verifying  : glibc-headers-2.12-1.166.el6_7.3.x86_64                     5/20 
  Verifying  : gcc-4.4.7-16.el6.x86_64                                     6/20 
  Verifying  : glibc-2.12-1.166.el6_7.3.x86_64                             7/20 
  Verifying  : 1:perl-Module-Pluggable-3.90-141.el6_7.1.x86_64             8/20 
  Verifying  : mpfr-2.4.1-6.el6.x86_64                                     9/20 
  Verifying  : 3:perl-version-0.77-141.el6_7.1.x86_64                     10/20 
  Verifying  : kernel-headers-2.6.32-573.8.1.el6.x86_64                   11/20 
  Verifying  : cpp-4.4.7-16.el6.x86_64                                    12/20 
  Verifying  : glibc-common-2.12-1.166.el6_7.3.x86_64                     13/20 
  Verifying  : 4:perl-libs-5.10.1-141.el6_7.1.x86_64                      14/20 
  Verifying  : libgcc-4.4.7-16.el6.x86_64                                 15/20 
  Verifying  : 4:perl-5.10.1-141.el6_7.1.x86_64                           16/20 
  Verifying  : glibc-2.12-1.149.el6.x86_64                                17/20 
  Verifying  : libgcc-4.4.7-11.el6.x86_64                                 18/20 
  Verifying  : glibc-common-2.12-1.149.el6.x86_64                         19/20 
  Verifying  : libgomp-4.4.7-11.el6.x86_64                                20/20 

Installed:
  gcc.x86_64 0:4.4.7-16.el6           perl.x86_64 4:5.10.1-141.el6_7.1          

Dependency Installed:
  cpp.x86_64 0:4.4.7-16.el6                                                     
  glibc-devel.x86_64 0:2.12-1.166.el6_7.3                                       
  glibc-headers.x86_64 0:2.12-1.166.el6_7.3                                     
  kernel-headers.x86_64 0:2.6.32-573.8.1.el6                                    
  mpfr.x86_64 0:2.4.1-6.el6                                                     
  perl-Module-Pluggable.x86_64 1:3.90-141.el6_7.1                               
  perl-Pod-Escapes.x86_64 1:1.04-141.el6_7.1                                    
  perl-Pod-Simple.x86_64 1:3.13-141.el6_7.1                                     
  perl-libs.x86_64 4:5.10.1-141.el6_7.1                                         
  perl-version.x86_64 3:0.77-141.el6_7.1                                        

Dependency Updated:
  glibc.x86_64 0:2.12-1.166.el6_7.3   glibc-common.x86_64 0:2.12-1.166.el6_7.3  
  libgcc.x86_64 0:4.4.7-16.el6        libgomp.x86_64 0:4.4.7-16.el6             

Complete!
Copy iso file /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
Installing Virtualbox Guest Additions 5.0.10 - guest version is 5.0.8
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.0.10 Guest Additions for Linux............
VirtualBox Guest Additions installer
Removing installed version 5.0.8 of VirtualBox Guest Additions...
Stopping VirtualBox Additions [FAILED]
(Cannot unload module vboxguest)
Removing existing VirtualBox non-DKMS kernel modules[  OK  ]
[  OK  ] VirtualBox Guest Addition service [  OK  ]
Copying additional installer modules ...
Installing additional modules ...
Removing existing VirtualBox non-DKMS kernel modules[  OK  ]
Building the VirtualBox Guest Additions kernel modules
The headers for the current running kernel were not found. If the following
module compilation fails then this could be the reason.
The missing package can be probably installed with
yum install kernel-devel-2.6.32-504.el6.x86_64

Building the main Guest Additions module[FAILED]
(Look at /var/log/vboxadd-install.log to find out what went wrong)
Doing non-kernel setup of the Guest Additions[  OK  ]
Installing the Window System drivers
Could not find the X.Org or XFree86 Window System, skipping.
An error occurred during installation of VirtualBox Guest Additions 5.0.10. Some functionality may not work as intended.
In most cases it is OK that the "Window System drivers" installation failed.
Restarting VM to apply changes...
==> default: Attempting graceful shutdown of VM...
==> 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: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /vagrant => /xxxxxxxxxxxxxxxxxxxx

Then below was displayed with red text.

Failed to mount folders in Linux guest. This is usually because
the "vboxsf" file system is not available. Please verify that
the guest additions are properly installed in the guest and
can work properly. The command attempted was:

mount -t vboxsf -o uid=`id -u vagrant`,gid=`getent group vagrant | cut -d: -f3` vagrant /vagrant
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` vagrant /vagrant

The error output from the last command was:

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

Above was displayed every vagrant reload.

But after vagrant ssh -c "sudo yum update -y", I succeeded to install Guest Additions via simply doing vagrant reload.

$ vagrant reload --no-provision
==> default: Attempting graceful shutdown of VM...
==> default: Checking if box 'boxcutter/centos66' 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: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
GuestAdditions versions on your host (5.0.10) and guest (5.0.8) do not match.
Loaded plugins: fastestmirror
Setting up Install Process
Loading mirror speeds from cached hostfile
 * base: ftp.iij.ad.jp
 * extras: ftp.iij.ad.jp
 * updates: ftp.iij.ad.jp
Package gcc-4.4.7-16.el6.x86_64 already installed and latest version
Package 1:make-3.81-20.el6.x86_64 already installed and latest version
Package 4:perl-5.10.1-141.el6_7.1.x86_64 already installed and latest version
Package bzip2-1.0.5-7.el6_0.x86_64 already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package kernel-devel.x86_64 0:2.6.32-573.8.1.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package            Arch         Version                    Repository     Size
================================================================================
Installing:
 kernel-devel       x86_64       2.6.32-573.8.1.el6         updates        10 M

Transaction Summary
================================================================================
Install       1 Package(s)

Total download size: 10 M
Installed size: 25 M
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : kernel-devel-2.6.32-573.8.1.el6.x86_64                       1/1 
  Verifying  : kernel-devel-2.6.32-573.8.1.el6.x86_64                       1/1 

Installed:
  kernel-devel.x86_64 0:2.6.32-573.8.1.el6                                      

Complete!
Copy iso file /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
Installing Virtualbox Guest Additions 5.0.10 - guest version is 5.0.8
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.0.10 Guest Additions for Linux............
VirtualBox Guest Additions installer
Removing installed version 5.0.10 of VirtualBox Guest Additions...
Stopping VirtualBox Additions [  OK  ]
Removing existing VirtualBox non-DKMS kernel modules[  OK  ]
Copying additional installer modules ...
Installing additional modules ...
Removing existing VirtualBox non-DKMS kernel modules[  OK  ]
Building the VirtualBox Guest Additions kernel modules
Building the main Guest Additions module[  OK  ]
Building the shared folder support module[  OK  ]
Building the OpenGL support module[FAILED]
(Look at /var/log/vboxadd-install.log to find out what went wrong. The module is not built but the others are.)
Doing non-kernel setup of the Guest Additions[  OK  ]
Starting the VirtualBox Guest Additions [  OK  ]
Installing the Window System drivers
Could not find the X.Org or XFree86 Window System, skipping.
An error occurred during installation of VirtualBox Guest Additions 5.0.10. Some functionality may not work as intended.
In most cases it is OK that the "Window System drivers" installation failed.
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /vagrant => /xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
==> default: Machine not provisioned because `--no-provision` is specified.

My shared folder has been mounted successfully.

$ vagrant ssh -c "ls /vagrant"
Vagrantfile  [...and other files]
Connection to 127.0.0.1 closed.

Can you update packages when creating the box for vbguest plugin?

install_vagrant_key: expected string, got bool

install_vagrant_key is defined as bool.

    "install_vagrant_key": true,

Packer (v0.8.0) is not happy about that.

$ make vmware/centos71
rm -rf output-vmware-iso
mkdir -p box/vmware
packer build -only=vmware-iso -var 'cm=nocm' -var 'headless=' -var 'update=' -var 'version=1.0.18' -var 'ssh_username=vagrant' -var 'ssh_password=vagrant' -var 'install_vagrant_key=true' -var 'iso_path=iso' centos71.json
Failed to parse template: 1 error(s) occurred:

* variable install_vagrant_key: '' expected type 'string', got unconvertible type 'bool'
make: *** [box/vmware/centos71-nocm-1.0.18.box] Error 1

$ packer version
Packer v0.8.0

Centos, please include kernel-headers and kernel-devel packages on virtualbox VM

On Vagrant box : 'boxcutter/centos68' (v2.0.21) for 'virtualbox'

Issue:
I can't run the box because the guest additions can not update.
The failure (deep down) is related to the need of kernel-headers and kernel-devel packages (to build those guest additions). And the fact Centos repos have been updated.

Context:
Today the box (v2.0.21) includes kernel packages on version 2.6.32-642.el6.
But Centos yum repos only have the packages on version 2.6.32-696.1.1.el6.

I have to update guest additions (a bug on my Virtualbox version made me update it, so I update the guest too).
In the process of installing those it detects missing package, tries to install those but the versions are incoherent. At the end, guest additions do not work anymore... and the VM is useless.
(An obvious workaround is not to update ... and it works)

issue.log.zip

Solving:
IMOO : it would be nice if the box already contains those packages kernel-headers and kernel-devel.

I'm too shy to publish a PR but I think it might be solved adding
yum install -y kernel-devel kernel-headers
on https://github.com/boxcutter/centos/blob/master/script/update.sh#L5

Why remove old box templates?

Why do 51234ad ?

Our team uses boxcutter/centos65, as the environment for our application is only certified up to this version of CentOS. And as the iso_url is still valid, why remove it?

Virtualbox VM GUI remains black

I've played a bit around with Packer and Virtualbox, but while vagrant ssh works as expected, the GUI remains black.

My Vagrantfile looks like this

Vagrant.configure("2") do |config|
  config.vm.box = "centos7-desktop"
  config.vm.box_version = "0"
  config.vm.hostname = "centos-dev"
  config.vm.synced_folder '.', '/vagrant', type: :virtualbox

  config.vm.provider :virtualbox do |vb|
    vb.name = "centos-dev"
    vb.gui = true
    vb.cpus = 2
    vb.memory = 4096
  end

  #config.vm.provision "shell", inline: <<-SHELL
  #	sudo yum -y groupinstall "GNOME Desktop"
  #	sudo systemctl set-default graphical.target
  #	sudo systemctl start graphical.target
  #SHELL
end

box-cutter/centos67 - vsn >=2.0.17 Problems

Hi - I've been using box-cutter/centos67 up to version 2.0.16 successfully, but from 2.0.17 onwards it fails to boot using Vagrant (so I've had to fix at 2.0.16 for now):

==> Booting VM...
==> Waiting for machine to boot. This may take a few minutes...
    SSH address: 127.0.0.1:2222
    SSH username: vagrant
    SSH auth method: private key
Timed out while waiting for the machine to boot.

I'm going to look through the 2.0.16 vs 2.0.17 diffs now, but any idea what the problem might be? FYI I'm using:

Vagrant 1.9.0
VirtualBox 5.1.10
Windows 10
Vagrant windows nfs plugin

Any help much appreciated.

empty /etc/machine-id on centos

Hi! Many thanks for maintaining those base images.
I noticed that the file /etc/machine-id was set to 2f59308c746c49e29cc2b9997ddb22da
Would it be possible to reset it to an empty file in the base image to make sure that systemd will reinitialise it?

Here is my current workaround:

    marcus.vm.provision :shell, name: 'set fleet_public_ip',
      inline: <<eos
      # The box we are using has unfortunately a hardcoded machine-id.
      # We must not have multiple machines in the cluster with the same machine-id.
      if [ "2f59308c746c49e29cc2b9997ddb22da" = "$(cat /etc/machine-id)" ]; then
        echo "Must reset the /etc/machine-id and reboot. Please run 'vagrant up marcus1 --provision' again"
        echo "" > /etc/machine-id
        sudo poweroff
      fi
eos

Thanks!

private_network breaks provisioning

I'm using boxcutter/centos72-desktop and if I add config.vm.network "private_network", ip: "172.16.193.100" to my Vagrantfile it will remain stuck on:

==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2200
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. 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.

The same happens when using public_network. When removing this directive everything works just fine.

This issue does not seem to be present with the centos/7 box.