Go to file
Daniel Kimsey 3b64620234 SSH tunneling support
Support for both local and remote TCP port tunneling. Includes updated
docs and tests.

Does not implement dynamic port forwarding (SSH's built-in SOCKS)
(uncertain difficulty) nor unix socket (potentially easy).
2019-09-18 11:09:41 -07:00
.circleci pin to go 1.13 & cleanup go deps 2019-09-05 17:11:08 +02:00
.github add debugging info to debugging page as well 2019-09-03 09:01:00 -07:00
builder Merge pull request #8106 from shapeblue-br/master 2019-09-17 10:15:09 -07:00
command Merge pull request #7960 from guidodobboletta/master 2019-08-12 16:32:29 -07:00
common use printf for logging 2019-09-13 01:53:42 +03:00
communicator SSH tunneling support 2019-09-18 11:09:41 -07: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 Rewrite all files, remove sensitive information 2019-08-09 15:00:23 +08:00
fix Move fixer test to fix package 2019-07-24 18:04:17 +01:00
helper SSH tunneling support 2019-09-18 11:09:41 -07:00
packer remove any reference to Push 2019-09-16 16:38:17 +02:00
plugin/example delete unneeded plugin file 2017-09-28 10:52:54 -07:00
post-processor fix post-processor 2019-09-16 13:45:28 -07:00
provisioner provisioner/inspec: Fix dropped error 2019-08-27 17:01:33 -07:00
scripts change installation of pigeon if off gopath 2019-07-01 12:16:50 -07:00
template remove any reference to Push 2019-09-16 16:38:17 +02:00
test SSH tunneling support 2019-09-18 11:09:41 -07:00
vendor update yandex-cloud/go-sdk & yandex-cloud/go-genproto 2019-09-10 18:52:55 +03:00
version update to 1.4.4-dev 2019-08-14 15:54:29 -07:00
website SSH tunneling support 2019-09-18 11:09:41 -07: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
CHANGELOG.md update changelog 2019-09-13 16:54:54 -07:00
CODEOWNERS Update CODEOWNERS 2019-09-04 14:42:15 +02: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 go get use enumer@master 2019-09-06 12:15:48 +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
checkpoint.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
commands.go implement a packer console analogous to the terraform console 2019-06-05 16:35:22 -07:00
config.go use port as ints 2019-03-19 15:01:12 +01:00
go.mod update yandex-cloud/go-sdk & yandex-cloud/go-genproto 2019-09-10 18:52:55 +03:00
go.sum update yandex-cloud/go-sdk & yandex-cloud/go-genproto 2019-09-10 18:52:55 +03:00
log.go deduplicate loglines that stream both to ui ERROR call and to streaming logs when PACKER_LOG=1 2019-07-25 16:33:02 -07: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.