Go to file
Adrien Delorme f555e7a9f2 allow a provisioner to timeout
* I had to contextualise Communicator.Start and RemoteCmd.StartWithUi
NOTE: Communicator.Start starts a RemoteCmd but RemoteCmd.StartWithUi will run the cmd and wait for a return, so I renamed StartWithUi to RunWithUi so that the intent is clearer.
Ideally in the future RunWithUi will be named back to StartWithUi and the exit status or wait funcs of the command will allow to wait for a return. If you do so please read carrefully https://golang.org/pkg/os/exec/#Cmd.Stdout to avoid a deadlock
* cmd.ExitStatus to cmd.ExitStatus() is now blocking to avoid race conditions
* also had to simplify StartWithUi
2019-04-08 20:09:21 +02:00
.circleci Revert "use golang:1.12 instead of cicleci/golang:1.12" 2019-03-04 11:17:58 +01:00
.github update contributing guidelines and make sure that the PR template links to them. 2019-01-23 11:35:50 -08:00
builder allow a provisioner to timeout 2019-04-08 20:09:21 +02:00
command Merge remote-tracking branch 'origin/master' into context_provisioner 2019-04-08 20:09:01 +02:00
common allow a provisioner to timeout 2019-04-08 20:09:21 +02:00
communicator allow a provisioner to timeout 2019-04-08 20:09:21 +02:00
contrib Document --except & --only flags for post-processors 2019-01-11 13:00:10 +01:00
examples Merge pull request #7375 from lrxcy/fix_190220 2019-03-05 09:41:49 -08: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 allow a provisioner to timeout 2019-04-08 20:09:21 +02:00
plugin/example delete unneeded plugin file 2017-09-28 10:52:54 -07:00
post-processor allow a provisioner to timeout 2019-04-08 20:09:21 +02:00
provisioner allow a provisioner to timeout 2019-04-08 20:09:21 +02:00
scripts scripts/build.sh: allow to set build settings when building 2019-02-19 15:10:30 +01:00
template Merge remote-tracking branch 'origin/master' into context_provisioner 2019-04-08 20:09:01 +02:00
test Add chroot in bats tests 2019-02-10 05:15:22 +01:00
vendor Add vendor 2019-04-04 15:20:46 -07:00
version update to v1.4.0-dev 2019-02-28 15:14:40 -08:00
website Merge pull request #7391 from carlpett/proxmox-builder 2019-04-08 09:54:11 -07:00
.gitattributes too many files for shell during Make, convert .go and .sh to EOL=lf 2018-04-07 05:22:39 -04:00
.gitignore switch to netlify deployment 2018-09-19 12:17:28 -07:00
.travis.yml building on go master is just wasting our time. 2019-04-04 14:56:53 -07:00
CHANGELOG.md update changelog 2019-04-05 10:39:46 -07:00
CODEOWNERS Merge branch 'master' into hyperone 2019-02-24 15:16:21 +01: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 increase timeout for tests to reduce flakiness in travis 2019-04-05 10:57:47 -07: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 Use the hashicorp/go-getter to download files 2019-03-13 12:11:58 +01: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 fix tty to avoid panic after resizing term near exit time 2019-04-02 10:18:46 +02:00
go.sum fix tty to avoid panic after resizing term near exit time 2019-04-02 10:18:46 +02:00
log.go Use Sprint() instead of Sprintf() in log dedupe 2018-10-09 22:43:54 -04:00
main.go Close tty on exit (#7411) 2019-03-15 11:10:30 +01: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

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.