Go to file
Tony b72a55a3fb
Update virtualbox-iso.html.md.erb
remove cpus/memory flags due to their property implementation, add vram for example
2019-05-20 10:09:45 -04:00
.circleci flag nightly builds as prerelease 2019-05-10 10:48:20 +02:00
.github Updating to suggested future-proof comment 2019-04-19 01:48:08 +00:00
builder refresh line endings 2019-05-17 14:58:20 -07:00
command simplify path parsing by making at string instead of an array + add tests 2019-05-07 11:51:21 +02:00
common common/net: Cleanup cache of used port after closing 2019-05-06 22:11:52 +01:00
communicator allow a provisioner to timeout 2019-04-08 20:09:21 +02:00
contrib prevent a breaking change so that we can merge the `-parallel-builds` option first. 2019-05-02 16:24:28 +02:00
examples refresh line endings 2019-05-17 14:58:20 -07:00
fix Merge pull request #7456 from hashicorp/do_5770 2019-04-05 09:12:20 -07:00
helper allow a provisioner to timeout 2019-04-08 20:09:21 +02:00
packer Add unit test to find issue #7655 2019-05-17 22:27:19 +00:00
plugin/example delete unneeded plugin file 2017-09-28 10:52:54 -07:00
post-processor update alicloud builder to use official SDK (#7477) 2019-04-26 10:37:49 +08:00
provisioner Check error returned from retry.Config.Run() 2019-05-17 22:28:34 +00:00
scripts refresh line endings 2019-05-17 14:58:20 -07:00
template allow to set provisioner timeout from buildfile 2019-04-08 20:09:21 +02:00
test Add Linode Images builder 2019-04-15 20:40:59 -04:00
vendor refresh line endings 2019-05-17 14:58:20 -07:00
version time to work towards 1.4.2 2019-05-16 09:02:32 +02:00
website Update virtualbox-iso.html.md.erb 2019-05-20 10:09:45 -04:00
.gitattributes refresh line endings 2019-05-17 14:58:20 -07:00
.gitignore switch to netlify deployment 2018-09-19 12:17:28 -07:00
.travis.yml add wait so osx builds dont time out 2019-05-10 09:41:03 -07:00
CHANGELOG.md time to work towards 1.4.2 2019-05-16 09:02:32 +02:00
CODEOWNERS add linode builder owners 2019-04-16 12:55:55 -04:00
Dockerfile dockerfile: add minimal image with provisioners support 2018-10-31 16:58:06 +03:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile check if running `go mod vendor` has an effect on vendor directory and if so fail 2019-04-11 14:19:25 +02:00
README.md Miscellaneous doc improvements 2018-10-18 19:09:49 -04:00
Vagrantfile vagrantfile: add support for docker provider 2018-10-31 16:58:06 +03:00
appveyor.yml appveyor: remove verbose mode as output is truncated, and I can't see what's wrong 2019-05-03 16:24:18 +02:00
checkpoint.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
commands.go Complete Atlas deprecation. 2018-08-02 20:23:28 -07:00
config.go use port as ints 2019-03-19 15:01:12 +01:00
go.mod vendor: github.com/hashicorp/go-version@v1.2.0 2019-05-06 22:28:27 +01:00
go.sum vendor: github.com/hashicorp/go-version@v1.2.0 2019-05-06 22:28:27 +01:00
log.go Use Sprint() instead of Sprintf() in log dedupe 2018-10-09 22:43:54 -04:00
main.go allow building packer on solaris by removing progress bar and tty imports 2019-05-07 15:58:49 +02:00
main_test.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
panic.go Add telemetry reporting through checkpoint 2017-06-15 13:21:11 -07:00
tty.go allow building packer on solaris by removing progress bar and tty imports 2019-05-07 15:58:49 +02:00
tty_solaris.go allow building packer on solaris by removing progress bar and tty imports 2019-05-07 15:58:49 +02:00

README.md

Packer

Build Status Windows Build Status GoDoc GoReportCard

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 many platforms, the full list of which can be found at https://www.packer.io/docs/builders/index.html.

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-af22d9b9",
    "instance_type": "t2.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:

https://www.packer.io/docs

Developing Packer

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