Downloads:

89,421

Downloads of v 0.8.6:

2,116

Last Update:

8/24/2015

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • Jack Pearkes
  • Mark Peek
  • Ross Smith II
  • Rickard von Essen

Tags:

packer vagrant virtual machine VM VirtualBox VMware puppet chef

Packer

This is not the latest version of Packer available.

0.8.6 | Updated: 8/24/2015

Downloads:

89,421

Downloads of v 0.8.6:

2,116

Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • Jack Pearkes
  • Mark Peek
  • Ross Smith II
  • Rickard von Essen

Packer 0.8.6

This is not the latest version of Packer available.

Some Checks Have Failed or Are Not Yet Complete

1 Test Unknown and 1 Passing Test


Validation Testing Unknown


Verification Testing Passed

Details

To install Packer, run the following command from the command line or from PowerShell:

>

To upgrade Packer, run the following command from the command line or from PowerShell:

>

To uninstall Packer, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade packer -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade packer -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure packer installed
  win_chocolatey:
    name: packer
    state: present
    version: 0.8.6
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'packer' do
  action    :install
  version  '0.8.6'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: packer,
    Version: 0.8.6,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller packer
{
   Name     = 'packer'
   Ensure   = 'Present'
   Version  = '0.8.6'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'packer':
  provider => 'chocolatey',
  ensure   => '0.8.6',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install packer version="0.8.6" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 8/24/2015.

Description

Packer is an open source tool for creating 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 does not replace configuration management like Chef or Puppet. In fact, when building images, Packer is able to use tools like Chef or Puppet to install software onto the image.


README.md
# packer

[![Latest version released](https://img.shields.io/chocolatey/v/packer.svg)](https://chocolatey.org/packages/packer)
[![Package downloads count](https://img.shields.io/chocolatey/dt/packer.svg)](https://chocolatey.org/packages/packer)

Chocolatey package for packer.

## Useful tips for maintain this package

With chocolatey package 0.8.0 I have changed the install location of packer to integrate it better into the Chocolatey directory structure. This improves the chocolatey experience. Right after installing the package, `packer.exe` is in your PATH.

This is done by the `ShimGen` feature which is some kind of symlink into the package directory. But for packer only one redirect is needed, only for the main `packer.exe`.
Chocolatey creates these symlinks for all exefiles found in the ZIP file. To suppress these symlinks I have added for all but `packer.exe` ignore files `packer-xyz.exe.ignore` into the `tools` directory.

This list of ignore files should be checked for each new packer release. 

1. Download new packer ZIP
2. List all files in the ZIP
3. create *.exe.ignore files for all files in the new packer.zip
tools\chocolateyInstall.ps1
$url = 'https://dl.bintray.com/mitchellh/packer/packer_0.8.6_windows_386.zip'
$checksum = '36d485f8368212906560174eacff193be1c76893'
$url64bit = 'https://dl.bintray.com/mitchellh/packer/packer_0.8.6_windows_amd64.zip'
$checksum64 = '05c19cc718dd84a9412d990dff309938130ec269'
$legacyLocation = "$env:SystemDrive\HashiCorp\packer"
$unzipLocation = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

Install-ChocolateyZipPackage "packer" "$url" "$unzipLocation" "$url64bit" `
 -checksum $checksum -checksumType 'sha1' -checksum64 $checksum64

If (Test-Path $legacyLocation) {
  Write-Host "Removing old packer installation from $legacyLocation"
  Remove-Item $legacyLocation -Force -Recurse
}
tools\packer-builder-amazon-chroot.exe.ignore
 
tools\packer-builder-amazon-ebs.exe.ignore
 
tools\packer-builder-amazon-instance.exe.ignore
 
tools\packer-builder-digitalocean.exe.ignore
 
tools\packer-builder-docker.exe.ignore
 
tools\packer-builder-file.exe.ignore
 
tools\packer-builder-googlecompute.exe.ignore
 
tools\packer-builder-null.exe.ignore
 
tools\packer-builder-openstack.exe.ignore
 
tools\packer-builder-parallels-iso.exe.ignore
 
tools\packer-builder-parallels-pvm.exe.ignore
 
tools\packer-builder-qemu.exe.ignore
 
tools\packer-builder-virtualbox-iso.exe.ignore
 
tools\packer-builder-virtualbox-ovf.exe.ignore
 
tools\packer-builder-vmware-iso.exe.ignore
 
tools\packer-builder-vmware-vmx.exe.ignore
 
tools\packer-post-processor-artifice.exe.ignore
 
tools\packer-post-processor-atlas.exe.ignore
 
tools\packer-post-processor-compress.exe.ignore
 
tools\packer-post-processor-docker-import.exe.ignore
 
tools\packer-post-processor-docker-push.exe.ignore
 
tools\packer-post-processor-docker-save.exe.ignore
 
tools\packer-post-processor-docker-tag.exe.ignore
 
tools\packer-post-processor-vagrant-cloud.exe.ignore
 
tools\packer-post-processor-vagrant.exe.ignore
 
tools\packer-post-processor-vsphere.exe.ignore
 
tools\packer-provisioner-ansible-local.exe.ignore
 
tools\packer-provisioner-chef-client.exe.ignore
 
tools\packer-provisioner-chef-solo.exe.ignore
 
tools\packer-provisioner-file.exe.ignore
 
tools\packer-provisioner-powershell.exe.ignore
 
tools\packer-provisioner-puppet-masterless.exe.ignore
 
tools\packer-provisioner-puppet-server.exe.ignore
 
tools\packer-provisioner-salt-masterless.exe.ignore
 
tools\packer-provisioner-shell-local.exe.ignore
 
tools\packer-provisioner-shell.exe.ignore
 
tools\packer-provisioner-windows-restart.exe.ignore
 
tools\packer-provisioner-windows-shell.exe.ignore
 

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Packer 1.4.3 4280 Thursday, August 22, 2019 Approved
Packer 1.4.2 7148 Saturday, June 29, 2019 Approved
Packer 1.4.1 5658 Friday, May 17, 2019 Approved
Packer 1.4.0 2439 Tuesday, April 16, 2019 Approved
Packer 1.3.5 3148 Thursday, March 7, 2019 Approved
Packer 1.3.4 2828 Tuesday, February 5, 2019 Approved
Packer 1.3.3.20181213 3231 Thursday, December 13, 2018 Approved
Packer 1.3.3 919 Sunday, December 9, 2018 Approved
Packer 1.3.2 2925 Wednesday, October 31, 2018 Approved

This package has no dependencies.

Discussion for the Packer Package

Ground Rules:

  • This discussion is only about Packer and the Packer package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Packer, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus