Go to file
Ian Duffy fa273f3bea Allow configurable VNC bind IP for QEMU
This commit allows for a user configurable VNC bind IP to be used for
QEMU.

By default this will be 127.0.0.1, alternatively, a user can use
0.0.0.0 which will bind to all interfaces.

This pull request should satisfy concerns of #3570 and #3559. It is
also in-line with the functionality provided by #3566 and #3565

Signed-off-by: Ian Duffy <ian@ianduffy.ie>
2016-05-25 10:10:12 +01:00
.github Accept only bug reports and feature requests 2016-04-11 12:55:11 +02:00
Godeps Update to go-autorest v7.0.5. (#3554) 2016-05-18 17:18:46 -07:00
builder Allow configurable VNC bind IP for QEMU 2016-05-25 10:10:12 +01:00
command initial import of checksum post-processor (#3492) 2016-05-18 17:31:16 -07:00
common Removed ftp/ftps schemas since they don't work. 2016-02-09 13:02:42 +01:00
communicator Swap width and height when allocating a pty 2016-04-06 15:40:19 -04:00
contrib Added sleeps to the azure-setup script so it is more likely to converge before running the next command 2016-03-14 20:08:36 -07:00
examples/azure Update samples. 2016-05-05 13:40:17 -07:00
fix Added fixer for ssh_key_path 2016-02-12 17:24:42 -08:00
helper Add winrm functionality to null provisioner (#2525) 2016-05-18 17:22:53 -07:00
packer file provisioner improvements 2016-02-12 11:48:28 -08:00
plugin/example Add example plugin for third-party plugin use 2016-03-16 16:42:24 -07:00
post-processor Resolves vsphere post-processor problems (#3321) 2016-05-18 18:26:46 -07:00
provisioner append ANSIBLE_HOST_KEY_CHECKING correctly (#3568) 2016-05-24 15:34:51 -07:00
scripts Go's -X linker flag now requires only one argument (#3540) 2016-05-17 13:24:04 -07:00
template Display better error messages on json.SyntaxError 2016-02-10 14:52:26 -05:00
test Add sftp file transfer support 2015-07-26 23:49:18 +00:00
vendor Update to go-autorest v7.0.5. (#3554) 2016-05-18 17:18:46 -07:00
version Update version to dev mode 2016-05-13 14:30:00 -07:00
website Allow configurable VNC bind IP for QEMU 2016-05-25 10:10:12 +01:00
.gitignore Build script for Windows. (#3481) 2016-05-05 13:12:17 -07:00
.travis.yml Remove go 1.4 from the build matrix 2016-03-14 21:00:23 -07:00
CHANGELOG.md Added disable_stop_intance to changelog 2016-05-24 15:42:33 -07:00
CONTRIBUTING.md Add note about only update what we need to update 2016-05-09 17:19:11 -07:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile Udpdated test/race timeouts to 2m because AWS seems to be taking a while 2016-05-06 23:15:05 -07:00
README.md Fix README build example to work out of box. 2016-03-16 22:16:35 -04:00
Vagrantfile Update go 1.5 references to 1.6 2016-02-17 16:29:38 -08:00
appveyor.yml Use the default version of Go. (#3498) 2016-05-04 15:53:36 -07:00
azure-merge.sh Added merge script to automatically pull in and fix the upstream repo 2016-03-14 20:08:12 -07:00
checkpoint.go Move version to its own package. (#3460) 2016-04-21 13:19:43 -07:00
commands.go Move version to its own package. (#3460) 2016-04-21 13:19:43 -07:00
config.go Switch osext package from mitchellh -> kardianos #2842 2015-11-04 12:36:00 -08:00
log.go command: move more to this package, remove old packages 2014-10-27 20:31:02 -07:00
main.go Move version to its own package. (#3460) 2016-04-21 13:19:43 -07:00
main_test.go Fatal -> Fatalf since we have a format string 2015-10-21 16:57:38 -07:00
panic.go Rename some files, style 2014-10-27 20:42:41 -07:00
signal.go add interrupt handling for SIGTERM [GH-1858] 2015-06-08 21:28:36 -07:00
stdin.go ctrl-c closes stdin for plugins so that they are unblocked 2013-07-25 23:27:13 -07:00

README.md

Packer

Build Status Windows Build Status

Packer is a tool for building identical machine images for multiple platforms from a single source configuration.

Packer is lightweight, runs on every major operating system, and is highly performant, creating machine images for multiple platforms in parallel. Packer comes out of the box with support for the following platforms:

  • Amazon EC2 (AMI). Both EBS-backed and instance-store AMIs
  • DigitalOcean
  • Docker
  • Google Compute Engine
  • OpenStack
  • Parallels
  • QEMU. Both KVM and Xen images.
  • VirtualBox
  • VMware

Support for other platforms can be added via plugins.

The images that Packer creates can easily be turned into Vagrant boxes.

Quick Start

Note: There is a great introduction and getting started guide for those with a bit more patience. Otherwise, the quick start below will get you up and running quickly, at the sacrifice of not explaining some key points.

First, download a pre-built Packer binary for your operating system or compile Packer yourself.

After Packer is installed, create your first template, which tells Packer what platforms to build images for and how you want to build them. In our case, we'll create a simple AMI that has Redis pre-installed. Save this file as quick-start.json. Export your AWS credentials as the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.

{
  "variables": {
    "access_key": "{{env `AWS_ACCESS_KEY_ID`}}",
    "secret_key": "{{env `AWS_SECRET_ACCESS_KEY`}}"
  },
  "builders": [{
    "type": "amazon-ebs",
    "access_key": "{{user `access_key`}}",
    "secret_key": "{{user `secret_key`}}",
    "region": "us-east-1",
    "source_ami": "ami-de0d9eb7",
    "instance_type": "t1.micro",
    "ssh_username": "ubuntu",
    "ami_name": "packer-example {{timestamp}}"
  }]
}

Next, tell Packer to build the image:

$ packer build quick-start.json
...

Packer will build an AMI according to the "quick-start" template. The AMI will be available in your AWS account. To delete the AMI, you must manually delete it using the AWS console. Packer builds your images, it does not manage their lifecycle. Where they go, how they're run, etc. is up to you.

Documentation

Comprehensive documentation is viewable on the Packer website:

http://www.packer.io/docs

Developing Packer

See CONTRIBUTING.md for best practices and instructions on setting up your development environment to work on Packer.