Skip to content

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

License

Notifications You must be signed in to change notification settings

EcaterinaGr/packer

This branch is 5283 commits behind hashicorp/packer:main.

Folders and files

NameName
Last commit message
Last commit date
Sep 5, 2019
Oct 29, 2019
Oct 30, 2019
Oct 23, 2019
Oct 15, 2019
Oct 24, 2019
Sep 18, 2019
Sep 26, 2019
Oct 21, 2019
Jul 24, 2019
Oct 16, 2019
Oct 15, 2019
Oct 15, 2019
Sep 28, 2017
Oct 28, 2019
Oct 15, 2019
Jul 1, 2019
Oct 23, 2019
Sep 18, 2019
Oct 29, 2019
Oct 1, 2019
Oct 29, 2019
May 17, 2019
Jun 5, 2019
Sep 27, 2019
Oct 29, 2019
Oct 8, 2019
Oct 31, 2018
Jun 24, 2013
Oct 16, 2019
Oct 18, 2018
Oct 31, 2018
Jun 6, 2019
Sep 19, 2019
Sep 18, 2019
Apr 4, 2017
Jun 5, 2019
Mar 19, 2019
Oct 29, 2019
Oct 29, 2019
Jul 25, 2019
Sep 18, 2019
Apr 4, 2017
Jun 15, 2017
May 7, 2019
May 7, 2019

Repository files navigation

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.

About

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

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Go 93.4%
  • HTML 5.4%
  • Shell 0.6%
  • CSS 0.3%
  • Ruby 0.1%
  • Makefile 0.1%
  • Other 0.1%