Re: [packer] Re: guix vagrant script stuck after reboot

[Bashid]

what topic i must explore when it's stick in error position? 

you troubleshoot ssh both from the host and inside the VM


What's you mean? is it possible to explain more?

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/394077e0-1514-49af-bb2a-9279dc0e9457%40googlegroups.com.

[packer] Packer v1.5.0 has been released

[Megan Marsh]

Hello Packer community!

We're very pleased to announce the release of Packer v1.5.0, the last 
release of 2019.  

*It contains two major new features: *

First, you can use HCL2 instead of json to define your Paceker templates, 
if you decide you would like to. If you don't want to mess with your 
templates, don't worry! We won't be deprecating json templates any time 
soon. Here is some documentation and examples to get you started: 
https://www.packer.io/guides/hcl

Second, special connection information like host and port of the 
provisioning instance, are now shared between builders and provisioners. 
You can access them using golang's templating engine. See the docs for 
details and an example: 
https://www.packer.io/docs/templates/engine.html#build

We also have a bunch of bug fixes and minor improvements.  For full 
details, see the changelog: 
https://github.com/hashicorp/packer/blob/master/CHANGELOG.md#150-december-18-2019
 

*There are two small backwards incompatabilites for everyday users:*

- The "clean_ami_name" template engine is now fully deprecated. Use 
"clean_resource_name" instead.
- The ansible-local "galaxycommand" option has been renamed to 
"galaxy_command".

For both of these incompatabilities, calling `packer fix` against your 
template will output a template with the necessary changes made so that you 
do not have to search for the fields to correct.

*There are some larger backwards incompatabilities for plugin maintainers*. 

Plugin maintainers will see that the interfaces of builders, provisioners, 
and post-processors have changed.

These changes are noted in the documentation for third party plugins; 
please refer to those documents to get your plugins back up to speed with 
the latest version of the Packer core. 

As always, please reach out to us via the GitHub issue tracker if you find 
anything wrong. 

We're really excited about the improvements that these changes will bring 
to the tool. Thanks for being such a great community to work for, and we 
hope you have a wonderful holiday season, no matter which ones you 
celebrate. 

Thanks
Megan and the Packer team

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/93d17630-badf-4788-aab2-8c5dddfc2472%40googlegroups.com.

Re: [packer] Re: List of valid "guest_os_type" values for vSphere builder?

[Emory Christenson]

I did that, didn't get me where I wanted to go somehow.

On Wednesday, December 18, 2019 at 10:53:51 AM UTC-8, Rickard von Essen 
wrote:
>
> I think the simplest way to find out is to manually create a VM with the 
> settings you want and then open the VMX file and check the content. 
>
> On Wed, Dec 18, 2019, 19:40 Emory Christenson  > wrote:
>
>> I managed to find a way to get the list from vCenter itself. That's not 
>> on there, I'll try it if the identifiers it listed don't get me anywhere. 
>> Thanks.
>>
>> On Wednesday, December 18, 2019 at 10:08:26 AM UTC-8, James Muldrow wrote:
>>>
>>> "windows9-64" worked for me for Server 2016.
>>>
>>> I have a working setup with instructions for Server 2016 on my github @ 
>>> https://github.com/jamesmuldrow/Server-2016_Template_for_Packer
>>>
>>> Im still building on it but its a decent start.
>>>
>>> On Wednesday, December 18, 2019 at 12:43:00 PM UTC-5, Emory Christenson 
>>> wrote:

 Hi, 

 No matter what I put for this value, our templates show up in vSphere 
 as “Other (32-bit).”
 I’ve even taking to trying to edit the VMX directly during our builds. 
 Nothing works.


 For Windows 2016 I’ve tried:
 windows9srv-64
 windows
 Windows2016_64
 etc, etc


 If anyone has any advice on how I can get the "Guest OS" field to 
 populate correctly in vSphere, I would really, really appreciate it.


 Thanks

>>> -- 
>> This mailing list is governed under the HashiCorp Community Guidelines - 
>> https://www.hashicorp.com/community-guidelines.html. Behavior in 
>> violation of those guidelines may result in your removal from this mailing 
>> list.
>>  
>> GitHub Issues: https://github.com/mitchellh/packer/issues
>> IRC: #packer-tool on Freenode
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Packer" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to packe...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/packer-tool/af43ec77-e50f-45e8-97d6-df341858a5d7%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/b5a56f29-e7e8-481b-af06-b22f8b157217%40googlegroups.com.

Re: [packer] Re: List of valid "guest_os_type" values for vSphere builder?

[Rickard von Essen]

I think the simplest way to find out is to manually create a VM with the
settings you want and then open the VMX file and check the content.

On Wed, Dec 18, 2019, 19:40 Emory Christenson  wrote:

> I managed to find a way to get the list from vCenter itself. That's not on
> there, I'll try it if the identifiers it listed don't get me anywhere.
> Thanks.
>
> On Wednesday, December 18, 2019 at 10:08:26 AM UTC-8, James Muldrow wrote:
>>
>> "windows9-64" worked for me for Server 2016.
>>
>> I have a working setup with instructions for Server 2016 on my github @
>> https://github.com/jamesmuldrow/Server-2016_Template_for_Packer
>>
>> Im still building on it but its a decent start.
>>
>> On Wednesday, December 18, 2019 at 12:43:00 PM UTC-5, Emory Christenson
>> wrote:
>>>
>>> Hi,
>>>
>>> No matter what I put for this value, our templates show up in vSphere as
>>> “Other (32-bit).”
>>> I’ve even taking to trying to edit the VMX directly during our builds.
>>> Nothing works.
>>>
>>>
>>> For Windows 2016 I’ve tried:
>>> windows9srv-64
>>> windows
>>> Windows2016_64
>>> etc, etc
>>>
>>>
>>> If anyone has any advice on how I can get the "Guest OS" field to
>>> populate correctly in vSphere, I would really, really appreciate it.
>>>
>>>
>>> Thanks
>>>
>> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Packer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to packer-tool+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/packer-tool/af43ec77-e50f-45e8-97d6-df341858a5d7%40googlegroups.com
> 
> .
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/CALz9Rt97zy-nYTxPC9JLTkg%2B0kSP6qy_6auAWEcAgUerVi%3D0KQ%40mail.gmail.com.

Re: [packer] Re: guix vagrant script stuck after reboot

[Rickard von Essen]

Run with flag --on-error=ask.

When if fails you troubleshoot ssh both from the host and inside the VM.
And don't run headless when troubleshooting.

On Wed, Dec 18, 2019, 12:38 Bashid  wrote:

> in below is also debug messages.
>
>
> 2019/12/18 11:28:41 packer: 2019/12/18 11:28:41 [INFO] 35 bytes written
> for 'uploadData'
> 2019/12/18 11:28:41 [INFO] 35 bytes written for 'uploadData'
> 2019/12/18 11:28:41 packer: 2019/12/18 11:28:41 [DEBUG] Opening new ssh
> session
> 2019/12/18 11:28:41 packer: 2019/12/18 11:28:41 [ERROR] ssh session open
> error: 'client not available', attempting reconnect
> 2019/12/18 11:28:41 packer: 2019/12/18 11:28:41 [DEBUG] reconnecting to
> TCP connection for SSH
> 2019/12/18 11:28:41 packer: 2019/12/18 11:28:41 [DEBUG] handshaking with
> SSH
> 2019/12/18
>  11:28:45 packer: 2019/12/18 11:28:45 Retryable error: Error uploading
> script: ssh: handshake failed: ssh: unable to authenticate, attempted
> methods [none password publickey], no supported methods remain
>
>
>
>
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Packer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to packer-tool+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/packer-tool/5f873f17-96ea-4318-a30d-01f1fae94c8b%40googlegroups.com
> 
> .
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/CALz9Rt_zfrWmhxa0OHryUDAPn5Su-dA7ek_F780FCH3745u86w%40mail.gmail.com.

Re: [packer] Re: Multi-stage builds

[Rickard von Essen]

No it doesn't have any built in support for multi stages. You have to have
different template files and build them in series.

For VM images there isn't usually any reason to build in multiple stages.
It's usually better to include "down streams" on the source level instead.

On Mon, Dec 16, 2019, 14:59 Loup Kreidl  wrote:

> Hello,
>
> This seems like an interesting idea to me!
>
> I've an extra use case to add to Max's one:
> We intend to use Packer to create our windows 10 ghost image and deploy it
> via PXE.
>
> To do so, we start from an iso and a VmWareIso builder, we apply the
> windows updates (+one or two tweaks) in this first build.
> Then we start a new packer build with a VmWareOvf builder that takes the
> artifact generated above. During this build we run the meat of our
> provisionning (installing softs via salt-masterless).
> And for the last build we also use the generated artifact but this time we
> are changing the VM's settings to boot via PXE so we can capture the VM.
>
> Since the two first step can take a while (up to 8h cumulated) if I can
> split those steps and have a "valid" artifact generated at each I can use
> those to make tests/changes on the next "layer" without having to rerun the
> whole process.
>
> We where wondering if packer could take another "packer-template" as a
> builder input and run successive builds by itself? (maybe this already
> exitst and we did not saw it?)
> Or maybe we are taking the wrong direction here?
>
> Best regards,
> Loup
>
> Le mercredi 23 octobre 2019 15:06:56 UTC+2, Max Weber a écrit :
>>
>> Hi,
>>
>> has Packer any kind of build-in support for multi-stage builds,
>> comparable to the one of Docker:
>>
>> https://docs.docker.com/develop/develop-images/multistage-build/
>>
>> At the moment I'm building a base image and use this one to build the
>> final image that contains my application. I only need to rebuild the base
>> image, when I install or update Linux packages or make changes that should
>> not be repeated on every normal build.
>>
>> Best regards,
>>
>> Max
>>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Packer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to packer-tool+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/packer-tool/925ff1e5-d1fa-4caf-85ad-db96c1a07be9%40googlegroups.com
> 
> .
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/CALz9Rt9Cd0Nan5NjWBObmBhpx8j9U1MSx%3Dy79wS8ypYcCt-c0w%40mail.gmail.com.

[packer] Re: List of valid "guest_os_type" values for vSphere builder?

[Emory Christenson]

I managed to find a way to get the list from vCenter itself. That's not on 
there, I'll try it if the identifiers it listed don't get me anywhere. 
Thanks.

On Wednesday, December 18, 2019 at 10:08:26 AM UTC-8, James Muldrow wrote:
>
> "windows9-64" worked for me for Server 2016.
>
> I have a working setup with instructions for Server 2016 on my github @ 
> https://github.com/jamesmuldrow/Server-2016_Template_for_Packer
>
> Im still building on it but its a decent start.
>
> On Wednesday, December 18, 2019 at 12:43:00 PM UTC-5, Emory Christenson 
> wrote:
>>
>> Hi, 
>>
>> No matter what I put for this value, our templates show up in vSphere as 
>> “Other (32-bit).”
>> I’ve even taking to trying to edit the VMX directly during our builds. 
>> Nothing works.
>>
>>
>> For Windows 2016 I’ve tried:
>> windows9srv-64
>> windows
>> Windows2016_64
>> etc, etc
>>
>>
>> If anyone has any advice on how I can get the "Guest OS" field to 
>> populate correctly in vSphere, I would really, really appreciate it.
>>
>>
>> Thanks
>>
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/af43ec77-e50f-45e8-97d6-df341858a5d7%40googlegroups.com.

[packer] Re: List of valid "guest_os_type" values for vSphere builder?

[James Muldrow]

"windows9-64" worked for me for Server 2016.

I have a working setup with instructions for Server 2016 on my github @ 
https://github.com/jamesmuldrow/Server-2016_Template_for_Packer

Im still building on it but its a decent start.

On Wednesday, December 18, 2019 at 12:43:00 PM UTC-5, Emory Christenson 
wrote:
>
> Hi, 
>
> No matter what I put for this value, our templates show up in vSphere as 
> “Other (32-bit).”
> I’ve even taking to trying to edit the VMX directly during our builds. 
> Nothing works.
>
>
> For Windows 2016 I’ve tried:
> windows9srv-64
> windows
> Windows2016_64
> etc, etc
>
>
> If anyone has any advice on how I can get the "Guest OS" field to populate 
> correctly in vSphere, I would really, really appreciate it.
>
>
> Thanks
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/648d63e8-1ef9-4a58-afc1-60a26e580480%40googlegroups.com.

[packer] List of valid "guest_os_type" values for vSphere builder?

[Emory Christenson]

Hi, 

No matter what I put for this value, our templates show up in vSphere as 
“Other (32-bit).”
I’ve even taking to trying to edit the VMX directly during our builds. 
Nothing works.


For Windows 2016 I’ve tried:
windows9srv-64
windows
Windows2016_64
etc, etc


If anyone has any advice on how I can get the "Guest OS" field to populate 
correctly in vSphere, I would really, really appreciate it.


Thanks

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/e03f321c-bf5a-465c-ab20-d6dfee49e554%40googlegroups.com.

[packer] Re: guix vagrant script stuck after reboot

[Bashid]

in below is also debug messages.


2019/12/18 11:28:41 packer: 2019/12/18 11:28:41 [INFO] 35 bytes written for 
'uploadData'
2019/12/18 11:28:41 [INFO] 35 bytes written for 'uploadData'
2019/12/18 11:28:41 packer: 2019/12/18 11:28:41 [DEBUG] Opening new ssh 
session
2019/12/18 11:28:41 packer: 2019/12/18 11:28:41 [ERROR] ssh session open 
error: 'client not available', attempting reconnect
2019/12/18 11:28:41 packer: 2019/12/18 11:28:41 [DEBUG] reconnecting to TCP 
connection for SSH
2019/12/18 11:28:41 packer: 2019/12/18 11:28:41 [DEBUG] handshaking with SSH
2019/12/18
 11:28:45 packer: 2019/12/18 11:28:45 Retryable error: Error uploading 
script: ssh: handshake failed: ssh: unable to authenticate, attempted 
methods [none password publickey], no supported methods remain





-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/5f873f17-96ea-4318-a30d-01f1fae94c8b%40googlegroups.com.

[packer] guix vagrant script stuck after reboot

[Bashid]

I run this 
 script 
with packer (with some modification), it's a script that generate custom 
guix image. The running is Ok until first reboot that i display at the end 
of below code.

{
"min_packer_version": "1.4.0",
"builders": [{
"type": "virtualbox-iso", 
"vm_name": "guixsd1",
"guest_os_type": "Linux_64",
"memory": 3000,
"headless": true,
"iso_url": "./guix-system-install-1.0.1.x86_64-linux.iso",  
 
"iso_checksum": 
"4ef645465464613513113ab17537bbead7fb41741e47fedab9451524a292a98de1",   
 
"iso_checksum_type": "sha256",  
   
"ssh_username": "root",
"ssh_password": "password",
"boot_command": [

"",
"passwd rootpasswordpassword",
"herd start ssh-daemon"
],
"ssh_timeout": "5m",
"shutdown_command": "shutdown"
}],
"provisioners": [
{
"type": "shell",
"inline": [
"parted -s --align=none /dev/sda mktable gpt mkpart primary 
ext2 0 100MB mkpart primary ext2 100MB 100% set 1 bios_grub on",
"mkfs.ext4 -L my-root /dev/sda2",
"mount LABEL=my-root /mnt",
"herd start cow-store /mnt",
"mkdir /mnt/etc"
]
},
{
"type": "file",
"source": "core-config.scm",
"generated": true,
"destination": "/mnt/etc/config.scm"
},
{
"type": "shell",
"inline": [
"guix system init /mnt/etc/config.scm /mnt",
"herd stop ssh-daemon"
]
},
{
"type": "shell",
"expect_disconnect": true,
"skip_clean": true,
"inline": ["reboot"]
},
{
"type": "shell",
"pause_before":"10s",
"inline": ["herd start ssh-daemon"]
},
.
.
.
[Other Commands]


After reboot. it's stuck and after 5 minutes (ssh timeout) i encounter with 
below error:

==> virtualbox-iso: copying to 
'/mnt'...   
   
  
virtualbox-iso: populating '/mnt'...
virtualbox-iso: bootloader successfully installed on '/dev/sda'
virtualbox-iso: Service ssh-daemon has been stopped.
==> virtualbox-iso: Provisioning with shell script: /tmp/packer-
shell108761660
==> virtualbox-iso: Pausing 10s before the next provisioner...
==> virtualbox-iso: Provisioning with shell script: /tmp/packer-
shell812273279
==> virtualbox-iso: Provisioning step had errors: Running the cleanup 
provisioner, if present...
==>
 virtualbox-iso: Deregistering and deleting 
VM...   
   
  
==> virtualbox-iso: Deleting output 
directory...   
   
  
Build 'virtualbox-iso' errored: Error uploading script: ssh: 
handshake failed: ssh: unable to authenticate, attempted methods 
[publickey none password], no supported methods 
remain 
 
  

  
  
==> Some builds didn't complete successfully and had 
errors: 
 
  
--> virtualbox-iso: Error uploading script: ssh: handshake 
failed: ssh: unable to authenticate, attempted methods [publickey none 
password], no supported methods 
remain 
 
  

  
  
==> Builds finished but no artifacts were created.

it seems that a ssh problem but how i could solve this?

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/278007ea-bae3-4ee6-9