Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Go to file
Juan Manuel Mesa 75efe3fcd1
Clean linting issues for packages template and interpolate (#9120)
6 years ago
.circleci Add RetriedProvisioner to allow retry provisioners (#9061) 6 years ago
.github Merge pull request #9006 from hashicorp/provisioner_acc_contributing 6 years ago
builder fix issue where -force is not working with vsphere builders (#9039) 6 years ago
cmd make docs a bit more readable for KeyValues too 6 years ago
command golang 1.14 doesn't like calling NewFile on existing files. Port solution over from Terraform 6 years ago
common HCL2: when we see a map generate an attribute spec instead of a block spec (#9035) 6 years ago
communicator packer.io prefix removal, html extension remove for in-code errors 6 years ago
contrib
examples
fix Fix gosimple S1005 linting issue (#8870) 6 years ago
hcl2template make sure keyvalue and namevalue filters are using the same naming as the service being used 6 years ago
helper golang 1.14 doesn't like calling NewFile on existing files. Port solution over from Terraform 6 years ago
packer Add RetriedProvisioner to allow retry provisioners (#9061) 6 years ago
plugin/example Add golangci-lint to project (#8686) 6 years ago
post-processor make sure keyvalue and namevalue filters are using the same naming as the service being used 6 years ago
provisioner Add `debug_mode` to PowerShell provisioner (#8996) 6 years ago
scripts scripts/build: Remove unsupported Freebsd/arm builds from build chain 6 years ago
template Clean linting issues for packages template and interpolate (#9120) 6 years ago
test
vendor [builder/azure-chroot] Shared image source (#9070) 6 years ago
version update to v1.5.6-dev 6 years ago
website update dependencies (#9111) 6 years ago
.codecov.yml Add after_n_builds to codecov.yml (#8913) 6 years ago
.gitattributes clean up documentation for new NIC and storage params 6 years ago
.gitignore
.golangci.yml Add golangci-lint to project (#8686) 6 years ago
.hashibot.hcl update hashibot config not to comment when locking super old and stale issues 6 years ago
CHANGELOG.md update changelog 6 years ago
CODEOWNERS add Hakujou as outscale code owner 6 years ago
Dockerfile
LICENSE
Makefile Revert golangci-lint to use new-from-rev pinned at 1.23.8 (#9072) 6 years ago
README.md Add Codecov badge and remove report style (#8896) 6 years ago
Vagrantfile
background_check.go
background_check_openbsd.go
checkpoint.go
commands.go
config.go make period stripping more strict so that users can disable provisiners by adding .old or whatever; this is pretty typical convention. 6 years ago
config_test.go Merge pull request #8616 from hashicorp/packer-plugin-path 6 years ago
go.mod Merge pull request #9104 from hashicorp/up_oci_sdk 6 years ago
go.sum Merge pull request #9104 from hashicorp/up_oci_sdk 6 years ago
log.go
main.go config: Fix loading external plugins from a packerconfig 6 years ago
main_test.go
panic.go
tty.go
tty_solaris.go

README.md

Packer

Build Status Windows Build Status GoDoc GoReportCard codecov

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.