github.com/hashicorp/packer@v1.14.3/README.md (about) 1 # Packer 2 [](LICENSE) 3 [](https://github.com/hashicorp/packer/actions/workflows/build.yml) 4 [](https://discuss.hashicorp.com/c/packer) 5 === 6 7 <p align="center" style="text-align:center;"> 8 <a href="https://www.packer.io"> 9 <img alt="HashiCorp Packer logo" src="website/public/img/logo-packer-padded.svg" width="500" /> 10 </a> 11 </p> 12 13 Packer is a tool for building identical machine images for multiple platforms 14 from a single source configuration. 15 16 Packer is lightweight, runs on every major operating system, and is highly 17 performant, creating machine images for multiple platforms in parallel. Packer 18 supports various platforms through external plugin integrations, the full list of which can 19 be found at https://developer.hashicorp.com/packer/integrations. 20 21 The images that Packer creates can easily be turned into [Vagrant](http://www.vagrantup.com) boxes. 22 23 ## Quick Start 24 25 ### Packer 26 27 There is a great [introduction and getting started guide](https://learn.hashicorp.com/tutorials/packer/get-started-install-cli) 28 for building a Docker image on your local machine without using any paid cloud resources. 29 30 Alternatively, you can refer to [getting started with AWS](https://developer.hashicorp.com/packer/tutorials/aws-get-started) to 31 learn how to build a machine image for an external cloud provider. 32 33 ### HCP Packer 34 35 HCP Packer registry stores Packer image metadata, enabling you to track your image lifecycle. 36 37 To get started with building an AWS machine image to HCP Packer for referencing in Terraform refer 38 to the collection of [HCP Packer Tutorials](https://developer.hashicorp.com/packer/tutorials/hcp-get-started). 39 40 ## Documentation 41 42 Comprehensive documentation is viewable on the Packer website at https://developer.hashicorp.com/packer/docs. 43 44 ## Contributing to Packer 45 46 See 47 [CONTRIBUTING.md](https://github.com/hashicorp/packer/blob/master/.github/CONTRIBUTING.md) 48 for best practices and instructions on setting up your development environment 49 to work on Packer. 50 51 ## Unmaintained Plugins 52 As contributors' circumstances change, development on a community maintained 53 plugin can slow. When this happens, HashiCorp may use GitHub's option to archive the 54 plugin’s repository, to clearly signal the plugin's status to users. 55 56 What does **unmaintained** mean? 57 58 1. The code repository and all commit history will still be available. 59 1. Documentation will remain on the Packer website. 60 1. Issues and pull requests are monitored as a best effort. 61 1. No active development will be performed by HashiCorp. 62 63 If you are interested in maintaining an unmaintained or archived plugin, please reach out to us at packer@hashicorp.com. 64 65