Re: [packer] Re: Azure windows virtual image provision Packer- winrm timeout issue

2020-01-19 Thread mohanapriya k1990 
I have tried the same. WinRM timeout is the issue when it is trying to 
connect to the VM provisioned. i have tried different images and increased 
timeout as well. It didn't help. Tried to login manually into the packer 
provisioned machine, WinRM is disabled. How can we enable the WinRM in 
Azure machines using packer?
For AWS, we are enabling the WinRM settings in user_data_file. Similarly 
for Azure do we have any option? 

On Friday, January 17, 2020 at 11:23:32 PM UTC+5:30, Alvaro Miranda 
Aguilera wrote:
>
> have you tried azure example?
>
> they use winrm
>
>
> https://docs.microsoft.com/en-us/azure/virtual-machines/windows/build-image-with-packer
>
>
> On Thu, Jan 16, 2020 at 11:30 AM mohanapriya k1990  > wrote:
>
>> Hi, Thanks for you reply. could you please mention where should i mention 
>> the winrm settings file in packer script for Azure.
>>
>> On Thursday, January 9, 2020 at 7:09:49 PM UTC+5:30, dragon788 wrote:
>>>
>>> Check out the boxstarter.org templates for bootstrapping Windows with 
>>> WinRM or look at the chef/bento repo on GitHub in the Windows folder to 
>>> find great examples.
>>
>> -- 
>> 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/8b577d8e-bdfb-4e3a-a2cd-ade57a19a8d6%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> Alvaro
>
>

-- 
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/0c56d864-5f01-4573-b1f7-536305dadb9d%40googlegroups.com.

Re: [packer] how to change the size of disk with Packer chroot builder?

2020-01-19 Thread Rodrigue Chakode 
By the way, I gave up and switched towards azure-arm builder - - even if
it's a a bit slower than azure-chroot.

Le dim. 19 janv. 2020 à 11:26, Rodrigue Chakode 
a écrit :

> Hi Richard,
> Thanks for your help.
>
> I tried that option (os_disk_size_gb), which shall be used with the option
> 'from_scratch' (I failed to understand values to provide for
> 'pre_mount_commands', also required in that case) :(
>
> For amazon-chroot builder, there is an option ('root_volume_size'
> [1]) which seems close to what I'm expecting,  but it's not supported by
> azure-chroot builder
>
> [1]
> https://www.packer.io/docs/builders/amazon-chroot.html#root_volume_size
>
> Rodrigue
>
>
> On Sun, Jan 19, 2020 at 10:59 AM Rickard von Essen <
> rickard.von.es...@gmail.com> wrote:
>
>> I have never used Azure but maybe this is the option you are looking for?
>>
>> https://packer.io/docs/builders/azure-chroot.html#os_disk_size_gb
>>
>> On Sun, Jan 19, 2020, 10:15 Rodrigue Chakode 
>> wrote:
>>
>>> Hello,
>>> Is it possible to change the default size of the device setup by Packer
>>> to build an image using chroot?
>>> Indeed, it seems that the size is fixed to 2Gb and in my case the
>>> provisionning script installs tools that make the disk full (causing the
>>> failing of the build).
>>>
>>> ==> azure-chroot: No apport report written because the error message
>>> indicates a disk full error
>>>
>>>
>>> https://groups.google.com/group/packer-tool
>>>
>>> Here is an extract of df -h
>>>
>>> /dev/sdd1   2.0G  1.7G  320M  84% /mnt/packer-azure-chroot-disks/sdd
>>>
>>> Thanks,
>>>
>>> Rodrigue
>>>
>>> --
>>> 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/8ed1bd67-8840-45f1-92b4-df3966d8c647%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/CALz9Rt8V-_WhkoF_yw1nn2tjrPSeS7Y9BEo%2BGYhiXKw4H4YkVg%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/CA%2BJEtC0uAOy%2BnaVw%3DgsDaSDzdQq3YkLYBSkH1wEtvO0WQB%3DHdw%40mail.gmail.com.

Re: [packer] how to change the size of disk with Packer chroot builder?

2020-01-19 Thread Rodrigue Chakode 
Hi Richard,
Thanks for your help.

I tried that option (os_disk_size_gb), which shall be used with the option
'from_scratch' (I failed to understand values to provide for
'pre_mount_commands', also required in that case) :(

For amazon-chroot builder, there is an option ('root_volume_size'
[1]) which seems close to what I'm expecting,  but it's not supported by
azure-chroot builder

[1] https://www.packer.io/docs/builders/amazon-chroot.html#root_volume_size

Rodrigue


On Sun, Jan 19, 2020 at 10:59 AM Rickard von Essen <
rickard.von.es...@gmail.com> wrote:

> I have never used Azure but maybe this is the option you are looking for?
>
> https://packer.io/docs/builders/azure-chroot.html#os_disk_size_gb
>
> On Sun, Jan 19, 2020, 10:15 Rodrigue Chakode 
> wrote:
>
>> Hello,
>> Is it possible to change the default size of the device setup by Packer
>> to build an image using chroot?
>> Indeed, it seems that the size is fixed to 2Gb and in my case the
>> provisionning script installs tools that make the disk full (causing the
>> failing of the build).
>>
>> ==> azure-chroot: No apport report written because the error message
>> indicates a disk full error
>>
>>
>> https://groups.google.com/group/packer-tool
>>
>> Here is an extract of df -h
>>
>> /dev/sdd1   2.0G  1.7G  320M  84% /mnt/packer-azure-chroot-disks/sdd
>>
>> Thanks,
>>
>> Rodrigue
>>
>> --
>> 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/8ed1bd67-8840-45f1-92b4-df3966d8c647%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/CALz9Rt8V-_WhkoF_yw1nn2tjrPSeS7Y9BEo%2BGYhiXKw4H4YkVg%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/CA%2BJEtC3t3wUQsv01U7djoP-1c%3DP4vFpKkJOFGnogXmW53Oan5w%40mail.gmail.com.

Re: [packer] how to change the size of disk with Packer chroot builder?

2020-01-19 Thread Rickard von Essen 
I have never used Azure but maybe this is the option you are looking for?

https://packer.io/docs/builders/azure-chroot.html#os_disk_size_gb

On Sun, Jan 19, 2020, 10:15 Rodrigue Chakode 
wrote:

> Hello,
> Is it possible to change the default size of the device setup by Packer to
> build an image using chroot?
> Indeed, it seems that the size is fixed to 2Gb and in my case the
> provisionning script installs tools that make the disk full (causing the
> failing of the build).
>
> ==> azure-chroot: No apport report written because the error message
> indicates a disk full error
>
>
> https://groups.google.com/group/packer-tool
>
> Here is an extract of df -h
>
> /dev/sdd1   2.0G  1.7G  320M  84% /mnt/packer-azure-chroot-disks/sdd
>
> Thanks,
>
> Rodrigue
>
> --
> 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/8ed1bd67-8840-45f1-92b4-df3966d8c647%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/CALz9Rt8V-_WhkoF_yw1nn2tjrPSeS7Y9BEo%2BGYhiXKw4H4YkVg%40mail.gmail.com.

[packer] how to change the size of disk with Packer chroot builder?

2020-01-19 Thread Rodrigue Chakode 
Hello,
Is it possible to change the default size of the device setup by Packer to 
build an image using chroot?
Indeed, it seems that the size is fixed to 2Gb and in my case the 
provisionning script installs tools that make the disk full (causing the 
failing of the build).

==> azure-chroot: No apport report written because the error message 
indicates a disk full error


https://groups.google.com/group/packer-tool

Here is an extract of df -h

/dev/sdd1   2.0G  1.7G  320M  84% /mnt/packer-azure-chroot-disks/sdd

Thanks,

Rodrigue

-- 
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/8ed1bd67-8840-45f1-92b4-df3966d8c647%40googlegroups.com.