[packer] Re: Help - CoreOS/Hyperv-iso not working # Timeout waiting for SSH.

[Andre Moraes (ICARO TECH)]

Hi,

  First, sorry for the delay. 
  If I got your point, looks like I need to setup a initial configuration 
to get SSH enable, so I follow some templates now and I'll test but I got 
stuck because of Memory issue in my laptop, I don't have enough memory to 
setup the VM, so I'm waiting for the IT guys get this done.
  Soon as I have this updated I'll keep here posted.

On Tuesday, October 8, 2019 at 1:56:17 PM UTC-3, Andre Moraes (ICARO TECH) 
wrote:
>
> Hello everyone,
>
> I’m new in Packer world and I’m stuck in a few days trying to create an 
> hyperv image using CoreOS as ‘iso’.
> Here’s the template that I’m using right now:
>
> {
> "description": "CoreOS image for a VirtualBox platform.",
>
> "builders": [{
>   "type": "hyperv-iso",
>   "iso_url": 
> "https://stable.release.core-os.net/amd64-usr/current/coreos_production_iso_image.iso;,
>   "iso_checksum": "5d41fe61404f298a87f303d766b84d3b",
>   "iso_checksum_type": "md5",
>   "ssh_username": "packer",
>   "ssh_password": "packer",
>   "vm_name": "testvm",
>   "memory": 3000,
>"ssh_timeout" : "10m",
>   "shutdown_command": "echo 'packer' | sudo -S shutdown -P now",
>   "boot_wait": "50s",
>   "http_directory": "./extra/files",
>   "boot_command": [
> "sudo -i",
> "systemctl stop sshd.socket",
> "wget http://{{ .HTTPIP }}:{{ .HTTPPort }}/install.yml",
> "coreos-install -d /dev/sda -C {{user `channel`}} -c install.yml",
>   "reboot"
>   ]
> }]
>
> }
>
> Error: [DEBUG] Error getting SSH address: No ip address
> Timeout waiting for SSH.
>
>
> Full packer_log attached.
>

-- 


Your privacy is important to us. That is why we have taken appropriate 
measures to ensure the data you provide to us is kept secure. To learn more 
about how we process your personal information, how we comply with 
applicable data protection laws, and care for the security and privacy of 
your personal data, please review our Privacy Policy 
.
 
If you have any questions related to data protection and compliance with 
applicable laws, please contact us at our Security Operations Center at 
1-302-444-9838 or mail us at: 

Attention: Privacy Compliance Program, P.O. 
Box 59263, Schaumburg, IL USA, 60159-0263

-- 
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/4c32c559-1651-4c44-8a04-4339d2d8f94c%40googlegroups.com.

Re: [packer] AWS Credential Passing Issue

[Rickard von Essen]

The packer program use your credentials to make API directly. Nor
credentials is passed to the EC2 instance launched. The canonical way of
giving it AWS API access is by using iam_instance_profile.

See https://packer.io/docs/builders/amazon-ebs.html#iam_instance_profile

On Wed, Oct 9, 2019, 15:21 CJ Ess  wrote:

> The documentation is a bit vague about how credential passing works. I've
> given the packer server all of the credentials it needs for the amazon ebs
> builder including iam:passrole for * resources in its instance profile, and
> I removed all other references to IAM from the json template. I noticed
> today that AWS cli commands running on the packer builder are failing
> because they can't determine their credentials.
>
> I was assuming that the key/secret/token was being passed to the packer
> builder, or that it would just use the profile of the packer builder. Is
> that not how it works?
>
> --
> 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/4e1e2710-a5fc-493a-ac30-b90719e1eedb%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/CALz9Rt9%2BR0jrX7NaF2fFp5XLDcWHORT33J%3DqF52kLmg%2BuKWkiA%40mail.gmail.com.

Re: [packer] Connecting to a kvm/qemu server

[Megan Marsh]

I believe that's accurate.

On Wed, Oct 9, 2019 at 8:47 AM Mauricio Tavares  wrote:

> I was reading https://www.packer.io/docs/builders/qemu.html and it does
> not mention a way to connect to a host running kvm to build thingies. Does
> that mean it only works if packer is local to the kvm server?
>
> --
> 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/f09c650f-c137-4572-b5ef-dcff92fad28f%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/CAGPV1urappHg9F4ZMvJwDdBS%2BvzL2r4YCBRLQuQWsXmXJ7sFfg%40mail.gmail.com.

[packer] AWS Credential Passing Issue

[CJ Ess]

The documentation is a bit vague about how credential passing works. I've 
given the packer server all of the credentials it needs for the amazon ebs 
builder including iam:passrole for * resources in its instance profile, and 
I removed all other references to IAM from the json template. I noticed 
today that AWS cli commands running on the packer builder are failing 
because they can't determine their credentials. 

I was assuming that the key/secret/token was being passed to the packer 
builder, or that it would just use the profile of the packer builder. Is 
that not how it works?

-- 
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/4e1e2710-a5fc-493a-ac30-b90719e1eedb%40googlegroups.com.

[packer] Re: ssh_name vs ssh_username

[Andre Moraes (ICARO TECH)]

Yes, it was.

On Wednesday, October 9, 2019 at 7:31:32 AM UTC-3, Mauricio Tavares wrote:
>
> Has ssh_name been deprecated for ssh_username?
>

-- 


Your privacy is important to us. That is why we have taken appropriate 
measures to ensure the data you provide to us is kept secure. To learn more 
about how we process your personal information, how we comply with 
applicable data protection laws, and care for the security and privacy of 
your personal data, please review our Privacy Policy 
.
 
If you have any questions related to data protection and compliance with 
applicable laws, please contact us at our Security Operations Center at 
1-302-444-9838 or mail us at: 

Attention: Privacy Compliance Program, P.O. 
Box 59263, Schaumburg, IL USA, 60159-0263

-- 
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/fd4c08af-3bc3-42fe-ac0c-c83cdaaeef41%40googlegroups.com.

[packer] ssh_name vs ssh_username

[Mauricio Tavares]

Has ssh_name been deprecated for ssh_username?

-- 
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/c3a69194-8cb2-4e7c-baa6-98682c8ee5e2%40googlegroups.com.