mirror of
https://github.com/hashicorp/packer.git
synced 2026-06-13 18:50:11 -04:00
50da6c8dc8
* Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Migrating links to new format * Updating docs-content-check-legacy-links-format hash * chore: update source * Update generated partials from Packer plugin SDK * Bump packer-plugin-sdk to get latest packer-sdc * Update website/content/docs/templates/hcl_templates/blocks/build/provisioner.mdx * Update Plugin SDK to fix shell-local regression --------- Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com> Co-authored-by: Wilken Rivera <wilken@hashicorp.com> Co-authored-by: Kendall Strautman <36613477+kendallstrautman@users.noreply.github.com>
30 lines
1.1 KiB
Text
30 lines
1.1 KiB
Text
---
|
|
description: |
|
|
Communicators are the mechanism Packer uses to upload files, execute
|
|
scripts, etc. with the machine being created.
|
|
page_title: Communicators
|
|
---
|
|
|
|
# Communicators
|
|
|
|
Communicators are the mechanism Packer uses to upload files, execute scripts,
|
|
etc. with the machine being created.
|
|
|
|
Communicators are configured within the
|
|
[builder](/packer/docs/templates/legacy_json_templates/builders) section. Packer currently supports
|
|
three kinds of communicators:
|
|
|
|
- `none` - No communicator will be used. If this is set, most provisioners
|
|
also can't be used.
|
|
|
|
- [ssh](/packer/docs/communicators/ssh) - An SSH connection will be established to the machine. This is
|
|
usually the default.
|
|
|
|
- [winrm](/packer/docs/communicators/winrm) - A WinRM connection will be established.
|
|
|
|
In addition to the above, some builders have custom communicators they can use.
|
|
For example, the Docker builder has a "docker" communicator that uses
|
|
`docker exec` and `docker cp` to execute scripts and copy files.
|
|
|
|
For more details on how to use each communicator, click the links above to be
|
|
taken to each communicator's page.
|