mirror of https://github.com/hashicorp/packer
trujillo-adam
1 year ago
parent
711a38bdd4
commit
da35666689
@ -1,14 +1,22 @@
|
||||
---
|
||||
description: |
|
||||
Community-maintained builders are not part of the core Packer binary, but
|
||||
can run alongside Packer with minimal extra effort.
|
||||
page_title: Community - Builders
|
||||
Community-supported builders are developed and maintained by third-parties and not HashiCorp. Use them with Packer to extend Packer functionality.
|
||||
page_title: Community-supported builders
|
||||
---
|
||||
|
||||
# Community Builders
|
||||
# Community-supported builders
|
||||
|
||||
The following builders are developed and maintained by various members of the
|
||||
Packer community, not by HashiCorp. For more information on how to use community
|
||||
builders, see our docs on [extending Packer](/packer/docs/plugins/creation).
|
||||
builders, refer to our docs on [extending Packer](/packer/docs/plugins/creation).
|
||||
|
||||
@include 'builders/community_builders.mdx'
|
||||
- ARM builders
|
||||
|
||||
- [packer-plugin-arm-image](https://github.com/solo-io/packer-plugin-arm-image): Lets you extend onto existing system images.
|
||||
- [packer-builder-arm](https://github.com/mkaczanowski/packer-builder-arm): Lets you extend or build new images with a variety of options, such as custom partition tables.
|
||||
|
||||
- [Exoscale builder](https://github.com/exoscale/packer-plugin-exoscale) - Creates Exoscale custom templates based on a compute instance snapshot.
|
||||
|
||||
- [Citrix XenServer/Citrix Hypervisor](https://github.com/xenserver/packer-builder-xenserver) - Plugin for creating [Citrix XenServer/Citrix Hypervisor](https://xenserver.org/) images from an ISO image or from an existing template.
|
||||
|
||||
- [XCP-NG/Citrix XenServer/Citrix Hypervisor/Updated Fork](https://github.com/ddelnano/packer-plugin-xenserver) - Plugin for creating [XCP-NG/Citrix XenServer/Citrix Hypervisor](https://xcp-ng.org/) images from an ISO image or from an existing template. This is a fork of the orginal and reccomended by the developers of XCP-NG.
|
||||
@ -1,15 +0,0 @@
|
||||
---
|
||||
description: |
|
||||
Packer is extensible, allowing you to write new builders without having to
|
||||
modify the core source code of Packer itself. Documentation for creating new
|
||||
builders is covered in the custom builders page of the Packer plugin section.
|
||||
page_title: Custom - Builders
|
||||
---
|
||||
|
||||
# Custom Builder
|
||||
|
||||
Packer is extensible, allowing you to write new builders without having to
|
||||
modify the core source code of Packer itself. Documentation for creating new
|
||||
builders is covered in the [custom
|
||||
builders](/packer/docs/plugins/creation/custom-builders) page of the Packer plugin
|
||||
section.
|
||||
@ -1,13 +0,0 @@
|
||||
---
|
||||
description: |
|
||||
Installing Packer is simple. You can download a precompiled binary or compile
|
||||
from source. This page details both methods.
|
||||
page_title: Install
|
||||
---
|
||||
|
||||
# Install Packer
|
||||
|
||||
For detailed instructions on how to install Packer, see [this
|
||||
Getting Started guide][install].
|
||||
|
||||
[install]: /packer/tutorials/docker-get-started/get-started-install-cli 'Install Packer'
|
||||
@ -1,64 +1,47 @@
|
||||
---
|
||||
description: >
|
||||
There are a handful of terms used throughout the Packer documentation where
|
||||
the
|
||||
|
||||
meaning may not be immediately obvious if you haven't used Packer before.
|
||||
|
||||
Luckily, there are relatively few. This page documents all the terminology
|
||||
|
||||
required to understand and use Packer. The terminology is in alphabetical
|
||||
order
|
||||
|
||||
for quick referencing.
|
||||
page_title: Terminology
|
||||
Packer and the Packer documentation uses a vocabulary of terms that have specific meaning. Learn about Packer terminology in this glossary.
|
||||
page_title: Packer terminology
|
||||
---
|
||||
|
||||
# Packer Terminology
|
||||
# Packer terminology
|
||||
|
||||
There are a handful of terms used throughout the Packer documentation where the
|
||||
meaning may not be immediately obvious if you haven't used Packer before.
|
||||
Luckily, there are relatively few. This page documents all the terminology
|
||||
required to understand and use Packer. The terminology is in alphabetical order
|
||||
for quick referencing.
|
||||
This page documents terminology we use throughout this documentation that have a specific meaning in Packer. These terms may not be immediately obvious if you have not used Packer before.
|
||||
|
||||
- `Artifacts` are the results of a single build, and are usually a set of IDs
|
||||
- _Artifacts_ are the results of a single build, and are usually a set of IDs
|
||||
or files to represent a machine image. Every builder produces a single
|
||||
artifact. As an example, in the case of the Amazon EC2 builder, the
|
||||
artifact is a set of AMI IDs (one per region). For the VMware builder, the
|
||||
artifact is a directory of files comprising the created virtual machine.
|
||||
|
||||
- `Builds` are a single task that eventually produces an artifact for a single
|
||||
- _Builds_ are a single task that eventually produces an artifact for a single
|
||||
platform. Multiple builds run in parallel. Example usage in a sentence:
|
||||
"The Packer build produced an AMI to run our web application." Or: "Packer
|
||||
is running the builds now for VMware, AWS, and VirtualBox."
|
||||
|
||||
- `Builders` are components of Packer that are able to create a machine image
|
||||
- _Builders_ are components of Packer that are able to create a machine image
|
||||
for a single platform. Builders read in some configuration and use that to
|
||||
run and generate a machine image. A builder is invoked as part of a build
|
||||
in order to create the actual resulting artifacts. Example builders include
|
||||
VirtualBox, VMware, and Amazon EC2.
|
||||
|
||||
- `Commands` are sub-commands for the `packer` program that perform some job.
|
||||
- _Commands_ are sub-commands for the `packer` program that perform a job.
|
||||
An example command is "build", which is invoked as `packer build`. Packer
|
||||
ships with a set of commands out of the box in order to define its
|
||||
command-line interface.
|
||||
|
||||
- `Data Sources` are components of Packer that fetch data from outside Packer
|
||||
- _Data sources_ are components of Packer that fetch data from outside Packer
|
||||
and make it available to use within the template.
|
||||
Example of data sources include Amazon AMI, and Amazon Secrets Manager.
|
||||
|
||||
- `Post-processors` are components of Packer that take the result of a
|
||||
- _Post-processors_ are components of Packer that take the result of a
|
||||
builder or another post-processor and process that to create a new
|
||||
artifact. Examples of post-processors are compress to compress artifacts,
|
||||
upload to upload artifacts, etc.
|
||||
|
||||
- `Provisioners` are components of Packer that install and configure software
|
||||
- _Provisioners_ are components of Packer that install and configure software
|
||||
within a running machine prior to that machine being turned into a static
|
||||
artifact. They perform the major work of making the artifact contain useful
|
||||
software. Example provisioners include shell scripts, Chef, Puppet, etc.
|
||||
|
||||
- `Templates` are either [HCL](https://packer.io/templates/hcl_templates) or JSON files which
|
||||
define one or more builds by configuring the various components of Packer.
|
||||
Packer is able to read a template and use that information to create
|
||||
multiple machine images in parallel.
|
||||
- _Templates_ are either [HCL](https://packer.io/templates/hcl_templates) or JSON files that define one or more builds by configuring the various components of Packer. Packer reads a template and uses the information to create multiple machine images in parallel.
|
||||
|
||||
@ -1,12 +0,0 @@
|
||||
### Community Builders
|
||||
|
||||
- ARM builders
|
||||
|
||||
- [packer-plugin-arm-image](https://github.com/solo-io/packer-plugin-arm-image) - simple builder lets you extend on existing system images.
|
||||
- [packer-builder-arm](https://github.com/mkaczanowski/packer-builder-arm) - flexible builder lets you extend or build images from scratch with variety of options (ie. custom partition table).
|
||||
|
||||
- [Exoscale builder](https://github.com/exoscale/packer-plugin-exoscale) - A builder to create Exoscale custom templates based on a Compute instance snapshot.
|
||||
|
||||
- [Citrix XenServer/Citrix Hypervisor](https://github.com/xenserver/packer-builder-xenserver) - Plugin for creating [Citrix XenServer/Citrix Hypervisor](https://xenserver.org/) images from an iso image or from an existing template.
|
||||
|
||||
- [XCP-NG/Citrix XenServer/Citrix Hypervisor/Updated Fork](https://github.com/ddelnano/packer-plugin-xenserver) - Plugin for creating [XCP-NG/Citrix XenServer/Citrix Hypervisor](https://xcp-ng.org/) images from an iso image or from an existing template. This is a fork of the orginal, and reccomended by the developers of XCP-NG.
|
||||
Loading…
Reference in new issue