Re: [packer] temporary_key_pair_name Applicability

[Jason Beranek]

To be clear, I didn’t mean it as a criticism, and appreciate the plans to
clean up the docs. I was thinking without considering the challenges of
things being auto generated that cleaning up the docs could be a good
starter task for external contributors.

-Jason


On Thu, Apr 2, 2020 at 13:22 Megan Marsh  wrote:

> We are aware that the documentation is wrong here. Sorry :( The issue is
> that the docs are autogenerated, so they're showing up even for builders
> where specific options aren't relevant. We're working on fixing them so
> that builders which don't use certain communicator features won't show them
> as though they're available.
>
> On Thu, Apr 2, 2020 at 10:16 AM Rickard von Essen <
> rickard.von.es...@gmail.com> wrote:
>
>> Actually this functionality has been extended a bit and it supports
>> VirtualBox now at least. See
>> https://packer.io/docs/builders/virtualbox-iso.html#ssh-key-pair-automation
>>
>> On Thu, Apr 2, 2020, 13:39 Jason Beranek  wrote:
>>
>>> Rickard,
>>>
>>> Probably worth a documentation update to capture the
>>> behavior/limitations.  I looked at the code, since I thought this was
>>> something that maybe used to work with the Virtualbox builders, and it
>>> looks like that code even generates the key pairs that it probably never
>>> uses.
>>>
>>> V/r,
>>>
>>> Jason A. Beranek
>>>
>>> On Thu, Apr 2, 2020 at 2:23 AM Rickard von Essen <
>>> rickard.von.es...@gmail.com> wrote:
>>>
 It's not applicable. It's just for builders where ssh public keys are
 served by the API to instances to that will be added by cloud-init (or
 something similar) will automatically add them to a authorized_keys file.

 On Thu, Apr 2, 2020, 04:15 Lesley Kimmel 
 wrote:

> I noticed that this SSH communicator option is available for several
> builders (based on the Packer docs). Specifically, I am using the
> vsphere-iso builder. I was playing with this option but it doesn't seem to
> do anything. When I search about it, it is generally in the context of
> Amazon builders. Is this option even applicable to the VMware builders? If
> so, how does it work?
>
> --
> 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/464b36a7-6d64-4227-86c0-4fb24c086e08%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/CALz9Rt9nTr190TrUnCb5v1p6%2BPN8ZyxHj0BoO1pWxRsvLhL3iQ%40mail.gmail.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/CAE_nh6nSOkQ5EqAfdEVgjAvQc6khDtwD48Mva2amo-akHfEg2Q%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> This mailing list is governed under the HashiCorp Community Guidelines

Re: [packer] temporary_key_pair_name Applicability

[Megan Marsh]

We are aware that the documentation is wrong here. Sorry :( The issue is
that the docs are autogenerated, so they're showing up even for builders
where specific options aren't relevant. We're working on fixing them so
that builders which don't use certain communicator features won't show them
as though they're available.

On Thu, Apr 2, 2020 at 10:16 AM Rickard von Essen <
rickard.von.es...@gmail.com> wrote:

> Actually this functionality has been extended a bit and it supports
> VirtualBox now at least. See
> https://packer.io/docs/builders/virtualbox-iso.html#ssh-key-pair-automation
>
> On Thu, Apr 2, 2020, 13:39 Jason Beranek  wrote:
>
>> Rickard,
>>
>> Probably worth a documentation update to capture the
>> behavior/limitations.  I looked at the code, since I thought this was
>> something that maybe used to work with the Virtualbox builders, and it
>> looks like that code even generates the key pairs that it probably never
>> uses.
>>
>> V/r,
>>
>> Jason A. Beranek
>>
>> On Thu, Apr 2, 2020 at 2:23 AM Rickard von Essen <
>> rickard.von.es...@gmail.com> wrote:
>>
>>> It's not applicable. It's just for builders where ssh public keys are
>>> served by the API to instances to that will be added by cloud-init (or
>>> something similar) will automatically add them to a authorized_keys file.
>>>
>>> On Thu, Apr 2, 2020, 04:15 Lesley Kimmel 
>>> wrote:
>>>
 I noticed that this SSH communicator option is available for several
 builders (based on the Packer docs). Specifically, I am using the
 vsphere-iso builder. I was playing with this option but it doesn't seem to
 do anything. When I search about it, it is generally in the context of
 Amazon builders. Is this option even applicable to the VMware builders? If
 so, how does it work?

 --
 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/464b36a7-6d64-4227-86c0-4fb24c086e08%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/CALz9Rt9nTr190TrUnCb5v1p6%2BPN8ZyxHj0BoO1pWxRsvLhL3iQ%40mail.gmail.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/CAE_nh6nSOkQ5EqAfdEVgjAvQc6khDtwD48Mva2amo-akHfEg2Q%40mail.gmail.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 a

Re: [packer] temporary_key_pair_name Applicability

[Rickard von Essen]

Actually this functionality has been extended a bit and it supports
VirtualBox now at least. See
https://packer.io/docs/builders/virtualbox-iso.html#ssh-key-pair-automation

On Thu, Apr 2, 2020, 13:39 Jason Beranek  wrote:

> Rickard,
>
> Probably worth a documentation update to capture the
> behavior/limitations.  I looked at the code, since I thought this was
> something that maybe used to work with the Virtualbox builders, and it
> looks like that code even generates the key pairs that it probably never
> uses.
>
> V/r,
>
> Jason A. Beranek
>
> On Thu, Apr 2, 2020 at 2:23 AM Rickard von Essen <
> rickard.von.es...@gmail.com> wrote:
>
>> It's not applicable. It's just for builders where ssh public keys are
>> served by the API to instances to that will be added by cloud-init (or
>> something similar) will automatically add them to a authorized_keys file.
>>
>> On Thu, Apr 2, 2020, 04:15 Lesley Kimmel 
>> wrote:
>>
>>> I noticed that this SSH communicator option is available for several
>>> builders (based on the Packer docs). Specifically, I am using the
>>> vsphere-iso builder. I was playing with this option but it doesn't seem to
>>> do anything. When I search about it, it is generally in the context of
>>> Amazon builders. Is this option even applicable to the VMware builders? If
>>> so, how does it work?
>>>
>>> --
>>> 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/464b36a7-6d64-4227-86c0-4fb24c086e08%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/CALz9Rt9nTr190TrUnCb5v1p6%2BPN8ZyxHj0BoO1pWxRsvLhL3iQ%40mail.gmail.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/CAE_nh6nSOkQ5EqAfdEVgjAvQc6khDtwD48Mva2amo-akHfEg2Q%40mail.gmail.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-7r%2BynA1dkLMkzYqbTzUYuEFy07CgLMoTiVGmB2EgN7g%40mail.gmail.com.

Re: [packer] Packer - Getting an Error When my Script executes in the provision for packer see below

[Dominic James]

Thx Megan! I inadvertently had clear in there for no reason. To be frank, i
don’t remember even putting it in there :), perhaps having too many
terminal envs opened & mysteriously clear ended up in my Visual code
session , my eyes were playing tricks on me. removed it and ran the
pipeline & its good! 👍🏾

On Wed, Apr 1, 2020 at 7:28 PM Megan Marsh  wrote:

> Hi Dominic,
>
> This is because of your call to "clear". Clear requires information about
> the terminal, which it isn't receiving. Just remove that call (It isn't
> really doing anything useful in an automated build anyway), and you should
> get unstuck.
>
> As a side note, you don't need to use the file provisioner to upload the
> shell script; Packer takes care of that for you as part of the shell
> provisioning. The "script" path provided is the path to the script on the
> machine running Packer, not on the remote machine being provisioned.
>
> Hopefully this helps. Reach out if you have any more issues getting set
> up, but this looks more like general scripting issues than a specific
> Packer issue.
>
>
> On Wed, Apr 1, 2020 at 1:11 PM Dominic James 
> wrote:
>
>> Packer template BELOW
>>
>> {
>> "variables": {
>> "aws_access_key": "{{env `PACKER_VAR_DEV_AWS_ACCESS_KEY_ID`}}",
>> "aws_secret_key": "{{env `PACKER_VAR_DEV_AWS_SECRET_ACCESS_KEY`}}"
>> },
>> "builders": [{
>> "type": "amazon-ebs",
>> "access_key": "{{user `aws_access_key`}}",
>> "secret_key": "{{user `aws_secret_key`}}",
>> "region": "us-east-1",
>> "source_ami_filter": {
>> "filters": {
>> "virtualization-type": "hvm",
>> "name": "Base-AMI-Ubuntu-*",
>> "root-device-type": "ebs"
>> },
>> "owners": [
>> "622297214873"
>> ],
>> "most_recent": true
>> },
>> "instance_type": "t2.large",
>> "ssh_username": "ubuntu",
>> "ami_name": "redacted-{{timestamp}}",
>> "vpc_id": "redacted",
>> "associate_public_ip_address": "true",
>> "subnet_id": "redacted"
>> }],
>> "provisioners": [{
>> "type": "file",
>> "source": "/tmp/redacted.sh",
>> "destination": "/tmp/redacted.sh"
>> },
>> {
>> "type": "shell",
>> "execute_command": "echo 'packer' | sudo -E sh -c '{{ .Vars }} {{ .Path
>> }}'",
>> "script": "/tmp/redacted.sh"
>> }]
>> }
>>
>> *redacted.sh script below*
>> #!/bin/bash -x
>>
>> ScriptPath="/tmp/"
>> ScriptName="runComposer.sh"
>>
>> set -ex
>> clear
>> sudo git clone --depth=1 --no-tags https://github.com/XX.git /tmp
>>
>> sleep 15
>> sudo chmod a+x $ScriptName
>> sleep 5
>> $ScriptPath/$ScriptName
>>
>> result=$?
>>
>>
>> *ERROR BELOW from PACKER DEBUG OUTPUT LOGGING*
>>
>> 2020/04/01 15:51:27 packer-builder-amazon-ebs plugin: [DEBUG] starting
>> remote command: echo 'packer' | sudo -E sh -c
>> 'PACKER_BUILDER_TYPE='amazon-ebs' PACKER_BUILD_NAME='amazon-ebs'
>> /tmp/script_883.sh' ==> amazon-ebs: + ScriptPath=/tmp/ ==> amazon-ebs: +
>> ScriptName=runComposer.sh ==> amazon-ebs: + set -ex ==> amazon-ebs: + clear
>> 2020/04/01 15:51:27 packer-builder-amazon-ebs plugin: [ERROR] Remote
>> command exited with '1': echo 'packer' | sudo -E sh -c
>> 'PACKER_BUILDER_TYPE='amazon-ebs' PACKER_BUILD_NAME='amazon-ebs'
>> /tmp/script_883.sh' 2020/04/01 15:51:27 packer-builder-amazon-ebs plugin:
>> [INFO] RPC endpoint: Communicator ended with: 1 2020/04/01 15:51:27 [INFO]
>> 0 bytes written for 'stdout' 2020/04/01 15:51:27 [INFO] 108 bytes written
>> for 'stderr' 2020/04/01 15:51:27 [INFO] RPC client: Communicator ended
>> with: 1 2020/04/01 15:51:27 [INFO] RPC endpoint: Communicator ended with: 1
>> 2020/04/01 15:51:27 packer-provisioner-shell plugin: [INFO] 0 bytes written
>> for 'stdout' 2020/04/01 15:51:27 packer-provisioner-shell plugin: [INFO]
>> 108 bytes written for 'stderr' 2020/04/01 15:51:27 packer-provisioner-shell
>> plugin: [INFO] RPC client: Communicator ended with: 1 ==> amazon-ebs:
>> 'unknown': I need something more specific.
>>
>> --
>> 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/251c6e60-4ba9-4674-bc87-94a39ae042e4%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-to

Re: [packer] temporary_key_pair_name Applicability

[Jason Beranek]

Rickard,

Probably worth a documentation update to capture the behavior/limitations.
I looked at the code, since I thought this was something that maybe used to
work with the Virtualbox builders, and it looks like that code even
generates the key pairs that it probably never uses.

V/r,

Jason A. Beranek

On Thu, Apr 2, 2020 at 2:23 AM Rickard von Essen <
rickard.von.es...@gmail.com> wrote:

> It's not applicable. It's just for builders where ssh public keys are
> served by the API to instances to that will be added by cloud-init (or
> something similar) will automatically add them to a authorized_keys file.
>
> On Thu, Apr 2, 2020, 04:15 Lesley Kimmel 
> wrote:
>
>> I noticed that this SSH communicator option is available for several
>> builders (based on the Packer docs). Specifically, I am using the
>> vsphere-iso builder. I was playing with this option but it doesn't seem to
>> do anything. When I search about it, it is generally in the context of
>> Amazon builders. Is this option even applicable to the VMware builders? If
>> so, how does it work?
>>
>> --
>> 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/464b36a7-6d64-4227-86c0-4fb24c086e08%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/CALz9Rt9nTr190TrUnCb5v1p6%2BPN8ZyxHj0BoO1pWxRsvLhL3iQ%40mail.gmail.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/CAE_nh6nSOkQ5EqAfdEVgjAvQc6khDtwD48Mva2amo-akHfEg2Q%40mail.gmail.com.

Re: [packer] temporary_key_pair_name Applicability

[Rickard von Essen]

It's not applicable. It's just for builders where ssh public keys are
served by the API to instances to that will be added by cloud-init (or
something similar) will automatically add them to a authorized_keys file.

On Thu, Apr 2, 2020, 04:15 Lesley Kimmel  wrote:

> I noticed that this SSH communicator option is available for several
> builders (based on the Packer docs). Specifically, I am using the
> vsphere-iso builder. I was playing with this option but it doesn't seem to
> do anything. When I search about it, it is generally in the context of
> Amazon builders. Is this option even applicable to the VMware builders? If
> so, how does it work?
>
> --
> 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/464b36a7-6d64-4227-86c0-4fb24c086e08%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/CALz9Rt9nTr190TrUnCb5v1p6%2BPN8ZyxHj0BoO1pWxRsvLhL3iQ%40mail.gmail.com.