Go to file
Adrien Delorme 6bbcd3e914
Remove remaining unused ssh config funcs and add missing calls (#6622)
* Remove duplicate unused SSHConfig funcs

* call to SSHConfigFunc() for azure/arm builder

* ncloud too

* remove empty ncloud file
2018-08-24 16:00:40 +02:00
.github Spelling & checks 2018-08-14 09:49:24 +02:00
builder Remove remaining unused ssh config funcs and add missing calls (#6622) 2018-08-24 16:00:40 +02:00
command replace scrubconfig with packer.LogSecretFilter.Set 2018-08-20 15:35:55 -07:00
common Merge pull request #6613 from hashicorp/merge_ssh_config_funcs 2018-08-23 16:03:36 -07:00
communicator make trailing slash still work 2018-07-12 09:08:36 -07:00
contrib Merge pull request #6566 from hashicorp/atlas-deprecation 2018-08-23 14:35:33 -07:00
examples Add ansible connection plugin examples 2018-07-10 17:10:53 -04:00
fix Ensure amazon-private-ip fixes string values 2018-07-05 16:57:54 +01:00
helper Merge pull request #6613 from hashicorp/merge_ssh_config_funcs 2018-08-23 16:03:36 -07:00
packer add tests for SensitiveVars 2018-08-21 10:28:22 -07:00
plugin/example delete unneeded plugin file 2017-09-28 10:52:54 -07:00
post-processor Merge pull request #6566 from hashicorp/atlas-deprecation 2018-08-23 14:35:33 -07:00
provisioner go back to using StartWithUI to prevent weird hangs during windows reboot 2018-08-23 16:15:50 -07:00
scripts use xargs to check for formatting 2018-05-01 20:39:48 -07:00
template add tests for SensitiveVars 2018-08-21 10:28:22 -07:00
test Add options to LXC builder for influencing for how containers are built and started 2017-10-30 21:48:43 -04:00
vendor Merge pull request #6566 from hashicorp/atlas-deprecation 2018-08-23 14:35:33 -07:00
version update to version 1.2.6-dev 2018-07-16 13:25:32 -07:00
website Merge pull request #6566 from hashicorp/atlas-deprecation 2018-08-23 14:35:33 -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 ignore Eclipse project files 2018-04-07 05:25:40 -04:00
.travis.yml add back in tests on latest go, but allow it to fail. 2018-06-28 14:49:09 -07:00
CHANGELOG.md update changelog 2018-08-23 14:21:40 -07:00
CODEOWNERS add scaleway codeowners 2018-02-12 11:18:50 -08:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile Check that only certain files are executable 2018-08-15 16:08:50 +02:00
README.md Remove `go get` from Quick Start as this isn't required to use Packer 2018-06-17 03:05:30 +01:00
Vagrantfile First cut at vagrant post-processor for docker 2018-07-06 17:11:24 -05:00
appveyor.yml fix appveyor 2017-06-06 11:52:21 -07: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 move packer to hashicorp 2017-04-04 13:39:01 -07:00
log.go deduplicate logs that stream to terminal 2018-08-21 15:24:17 -07:00
main.go PoC for filtering logs 2018-08-20 15:20:21 -07: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
stdin.go Gracefully clean up on SIGTERM 2017-09-08 11:42:32 -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.