geerlingguy / packer-ubuntu-1404 Goto Github PK

DEPRECATED - Packer Example - Ubuntu 14.04 Vagrant Box using Ansible provisioner

Home Page: https://app.vagrantup.com/geerlingguy/boxes/ubuntu1404

Shell 100.00%

packer vagrant virtualbox box ansible ubuntu ubuntu1404 lts minimal iso

packer-ubuntu-1404's Introduction

Packer Example - Ubuntu 14.04 minimal Vagrant Box

DEPRECATED: This project is no longer maintained, and though the base box is still available on Vagrant Cloud/Atlas, it will not be updated anymore as of 2019. Ubuntu 14.04 no longer receives active support from Canonical, therefore any users still running this version should upgrade to a newer, supported Ubuntu release.

Current Ubuntu Version Used: 14.04.5

Pre-built Vagrant Box:

vagrant init geerlingguy/ubuntu1404
See older versions: http://files.midwesternmac.com/

This example build configuration installs and configures Ubuntu 14.04 x86_64 minimal using Ansible, and then generates a Vagrant box file for VirtualBox.

The example can be modified to use more Ansible roles, plays, and included playbooks to fully configure (or partially) configure a box file suitable for deployment for development environments.

Requirements

The following software must be installed/present on your local machine before you can use Packer to build the Vagrant box file:

Packer
Vagrant
VirtualBox (if you want to build the VirtualBox box)
Ansible

Usage

Make sure all the required software (listed above) is installed, then cd to the directory containing this README.md file, and run:

$ packer build -var 'version=1.2.0' ubuntu1404.json

After a few minutes, Packer should tell you the box was generated successfully, and the box was uploaded to Vagrant Cloud.

Note: This configuration includes a post-processor that pushes the built box to Vagrant Cloud (which requires a VAGRANT_CLOUD_TOKEN environment variable to be set); remove the vagrant-cloud post-processor from the Packer template to build the box locally and not push it to Vagrant Cloud. You don't need to specify a version variable either, if not using the vagrant-cloud post-processor.

Testing built boxes

There's an included Vagrantfile that allows quick testing of the built Vagrant boxes. From this same directory, run the following command after building the box:

$ vagrant up

License

MIT license.

Author Information

Created in 2014 by Jeff Geerling, author of Ansible for DevOps.

packer-ubuntu-1404's People

Contributors

Stargazers

Watchers

packer-ubuntu-1404's Issues

Build fails due to Galaxy certificate issue and VirtualBox Guest Additions Installer hangs

See related: geerlingguy/packer-centos-6#15

Basically, Ubuntu 14.04's apt repos ship with a version of Python too old to support SNI. Easiest fix since 14.04 is so old and I don't want to try to replace system Python with something more advanced is to pass the -c option to the ansible-galaxy command like so:

"galaxycommand": "ansible-galaxy -c"

Make sure all the Ansible packages are removed

For the VMware Fusion box (at least), I get the following when performing apt commands inside the generated box:

The following packages were automatically installed and are no longer required:
  libyaml-0-2 python-crypto python-httplib2 python-jinja2 python-markupsafe
  python-paramiko python-pkg-resources python-support python-yaml sshpass
Use 'apt-get autoremove' to remove them.

Support for vmware provider?

Hi Jeff,

We're switching to vmware as a provider for performance reasons. I tried to install your drupal-dev-vm, which currently points to https://atlas.hashicorp.com/geerlingguy/boxes/ubuntu1404, but that only offers the virtualbox provider. I'm not sure what it would take to support another provider, or if this repo is the one that you deploy to the Atlas, but if it's not difficult to support vmware, I'd love you to add it.

Thanks!

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

Remove VMware Fusion support

Since I haven't updated that box, nor even have Fusion anymore... I am not willing to maintain support for it in this project.

Overly complex boot command

Hi, I used your build as a template for my own purposes.

I ended up reducing the boot command to the following:

      "boot_command": [
        "<esc><wait>",
        "<esc><wait>",
        "<enter><wait>",
        "/install/vmlinuz",
        " auto=true",
        " priority=critical",
        " initrd=/install/initrd.gz",
        " url=http://{{ .HTTPIP }}:{{ .HTTPPort }}/preseed.cfg",
        " -- ",
        "<enter>"
      ],

and putting the following in my preseed.cfg

d-i debian-installer/locale string en_US

d-i console-setup/ask_detect boolean false

d-i keyboard-configuration/modelcode string pc105
d-i keyboard-configuration/layoutcode string us

Results are the same as your current configuration but pushes the decision to the preseed.cfg which is easier to maintain/manage.

Cheers!

PS Thanks for the great template to get me started! I've never used Ubuntu before.

Build fails due to order of setup/ansible.sh scripts

The open-vm-tools package prevent installing VMware Tools

I'm opening an issue here but it can be related to ansible-role-packer-debian.

I've updated the ubuntu1404.json to the newest iso

      "iso_urls": [
        "iso/ubuntu-14.04.5-server-amd64.iso",
        "http://releases.ubuntu.com/14.04/ubuntu-14.04.5-server-amd64.iso"
      ],
      "iso_checksum_type": "sha256",
      "iso_checksum": "dde07d37647a1d2d9247e33f14e91acb10445a97578384896b4e1d985f754cc1",

and try build vmware box.

I receive an error

    vmware-iso: TASK [geerlingguy.packer-debian : Run the VMware tools installer.] *************
    vmware-iso: fatal: [127.0.0.1]: FAILED! => {"changed": true, "cmd": "/tmp/vmfusion-archive/vmware-tools-distrib/vmware-install.pl --default", "delta": "0:00:00.075623", "end": "2017-05-20 06:33:49.173368", "failed": true, "rc": 1, "start": "2017-05-20 06:33:49.097745", "stderr": "", "stderr_lines": [], "stdout": "The installer has detected an existing installation of open-vm-tools packages \non this system and will not attempt to remove and replace these user-space \napplications. It is recommended to use the open-vm-tools packages provided by \nthe operating system. If you do not want to use the existing installation of \nopen-vm-tools packages and use VMware Tools, you must uninstall the \nopen-vm-tools packages and re-run this installer.\nThe packages that need to be removed are:\nopen-vm-tools\nThe installer will next check if there are any missing kernel drivers. Type yes\nif you want to do this, otherwise type no [yes] \n\nFor kernels >= 4.0.0, the open-vm-tools packages need to be of version 10.0.0 \nor higher for VMware Host Guest Filessystem (vmhgfs) to function with VMware \nTools. Please upgrade open-vm-tools packages and rerun this installer, or \nuninstall open-vm-tools packages. Alternatively, you can disable using vmhgfs \nwhen VMware Tools are configured.\n\nEnter yes to proceed. [no] \n\nExecution aborted.", "stdout_lines": ["The installer has detected an existing installation of open-vm-tools packages ", "on this system and will not attempt to remove and replace these user-space ", "applications. It is recommended to use the open-vm-tools packages provided by ", "the operating system. If you do not want to use the existing installation of ", "open-vm-tools packages and use VMware Tools, you must uninstall the ", "open-vm-tools packages and re-run this installer.", "The packages that need to be removed are:", "open-vm-tools", "The installer will next check if there are any missing kernel drivers. Type yes", "if you want to do this, otherwise type no [yes] ", "", "For kernels >= 4.0.0, the open-vm-tools packages need to be of version 10.0.0 ", "or higher for VMware Host Guest Filessystem (vmhgfs) to function with VMware ", "Tools. Please upgrade open-vm-tools packages and rerun this installer, or ", "uninstall open-vm-tools packages. Alternatively, you can disable using vmhgfs ", "when VMware Tools are configured.", "", "Enter yes to proceed. [no] ", "", "Execution aborted."]}
    vmware-iso: to retry, use: --limit @/tmp/packer-provisioner-ansible-local/591fe151-7d7a-f700-ac81-1ae7390add50/main.retry
    vmware-iso:

I tried find in which step the open-vm-tools packages is installed to prevent it but without success.

When I initialized unattended installation of Ubuntu - using boot parameter and preseed.cfg file open-vm-tools were not installed.

I don't understand :-(

Can you look on this too? Thank you.

Update to 14.04.5

It is available.

Resolve 'Waiting for HGFS kernel module to load' error for VMWare

See: Error Waiting for HGFS kernel module to load during vagrant up --provider=vmware_fusion. This seems to be a problem with both this and the 12.04 version of the Packer-built box, and only occurs when using native shared folders (the problem goes away when using NFS).

Unable to use with VMWare Fusion

When I try and vagrant up --provider=vmware_fusion with the following Vagrantfile: https://github.com/NuCivic/ansible-dev-vm/blob/move-to-geerlinguy140/Vagrantfile

I get:

$ vagrant up --provider=vmware_fusion
Bringing machine 'devbox' up with 'vmware_fusion' provider...
==> devbox: Box 'geerlingguy/ubuntu1404' could not be found. Attempting to find and install...
    devbox: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation
    devbox: Box Version: >= 0
==> devbox: Adding box 'geerlingguy/ubuntu1404' (v0) for provider: vmware_desktop, vmware_fusion, vmware_workstation
    devbox: Downloading: https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box
The box you attempted to add doesn't match the provider you specified.

Provider expected: vmware_desktop, vmware_fusion, vmware_workstation
Provider of box: virtualbox

It says the provider of the box is virtualbox, even I I use the URL http://files.midwesternmac.com/boxes/VMware-ubuntu1404-104.box

Any idea what the issue is? Thanks.