Where we define source image and destination image details while automating the image creation using packer

Question

Where we define source image and destination image details while automating the image creation using packer

Varma 1,495

Where we create a source image and destination image version details to be created in the following JSON file mentioning the following document? https://learn.microsoft.com/en-us/azure/virtual-machines/windows/build-image-with-packer FYI: I have gallery where image are exist COuld you please provide me updated template where I should be able to provde source image details and destination image details. I am planning to do with JSON.

Martin Therkelsen 1,410 Reputation points MVP

2024-02-07T09:03:53.1633333+00:00

Hi Varma, I am not sure what you are asking. Are you missing where to put the target gallery in the JSON file?
Varma 1,495 Reputation points

2024-02-07T09:21:01.9366667+00:00

HI Martin, Thank you for the response. in the given JSON template, I am not sure where to pass the values of compute gallery that includes Source gallery name , source VM image defintion and VM version and then same destination details VM version details, I am going to create new image in the same gallery For example here is source gallery from there I take 1.0.0 image and then after packer does it steps I should see 1.0.2 in the same gallery

Hope you have understood Could you please provide an update template with above deatils as I am not clear of where I should those details as document did not give that information
Martin Therkelsen 1,410 Reputation points MVP

2024-02-07T09:26:38.9333333+00:00

Hi Varma. I get your question now. Thanks for clarifying. I don't have a direct answer for you now, but I will look into it. The way I normally do new images is to use Azure Market Places offers as the base and add the software I need. This will ensure a clean base without custom software and then capture it to the compute gallery. I will try to see if we can specify the compute gallery as a source so you can achieve what you want.
Varma 1,495 Reputation points

2024-02-07T09:32:30.24+00:00

Thank you Martin, Looking Forword to hear from you.
kobulloc-MSFT 26,801 Reputation points Microsoft Employee Moderator

2024-02-09T08:21:41.3466667+00:00

Hello, @Varma !

If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If you have additional questions, please start a new thread so the question can be answered. Thank you for helping to improve Microsoft Q&A!

Accepted answer

0 additional answers

Your answer

Martin Therkelsen 1,410 Reputation points MVP

2024-02-07T09:03:53.1633333+00:00

Hi Varma, I am not sure what you are asking. Are you missing where to put the target gallery in the JSON file?
Varma 1,495 Reputation points

2024-02-07T09:21:01.9366667+00:00

HI Martin, Thank you for the response. in the given JSON template, I am not sure where to pass the values of compute gallery that includes Source gallery name , source VM image defintion and VM version and then same destination details VM version details, I am going to create new image in the same gallery For example here is source gallery from there I take 1.0.0 image and then after packer does it steps I should see 1.0.2 in the same gallery

Hope you have understood Could you please provide an update template with above deatils as I am not clear of where I should those details as document did not give that information
Martin Therkelsen 1,410 Reputation points MVP

2024-02-07T09:26:38.9333333+00:00

Hi Varma. I get your question now. Thanks for clarifying. I don't have a direct answer for you now, but I will look into it. The way I normally do new images is to use Azure Market Places offers as the base and add the software I need. This will ensure a clean base without custom software and then capture it to the compute gallery. I will try to see if we can specify the compute gallery as a source so you can achieve what you want.
Varma 1,495 Reputation points

2024-02-07T09:32:30.24+00:00

Thank you Martin, Looking Forword to hear from you.
kobulloc-MSFT 26,801 Reputation points Microsoft Employee Moderator

2024-02-09T08:21:41.3466667+00:00

Hello, @Varma !

If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If you have additional questions, please start a new thread so the question can be answered. Thank you for helping to improve Microsoft Q&A!

Answer 1

Martin Therkelsen 1,410 MVP

You can use this JSON to deploy and image from Azure Compute Gallery and also capture it to Azure Compute Gallery.

{
    "builders": [
        {
            "type": "azure-arm",
            "client_id": "",
            "client_secret": "",
            "tenant_id": "",
            "subscription_id": "",
            "shared_image_gallery": {
                "subscription": "",
                "resource_group": "rg-avd-images",
                "gallery_name": "gal_avd",
                "image_name": "avd_w11",
                "image_version": "1.0.0"
            },
            "shared_image_gallery_destination": {
                "subscription": "",
                "resource_group": "rg-avd-images",
                "gallery_name": "gal_avd",
                "image_name": "avd_w11_new",
                "image_version": "1.0.0",
                "replication_regions": ["WestEurope"],
                "storage_account_type": "Standard_LRS"
            },
            "build_resource_group_name": "myPackerGroup",
            "os_type": "Windows",
            "vm_size": "Standard_D4s_v5",
            "winrm_insecure": true,
            "winrm_timeout": "5m",
            "winrm_use_ssl": true,
            "winrm_username": "packer"
        }
    ]    
}

Martin Therkelsen 1,410 MVP

You can also use the HCL format instead of JSON if you want to. That will look like the code below.

source "azure-arm" "autogenerated_1" {
  build_resource_group_name         = "myPackerGroup"
  client_id                         = ""
  client_secret                     = ""
  communicator                      = "winrm"

  shared_image_gallery {
    subscription = ""
    resource_group = "rg-avd-images"
    gallery_name = "gal_avd"
    image_name = "avd_w11"
    image_version = "1.0.0"
  }
  shared_image_gallery_destination {
    subscription = ""
    resource_group = "rg-avd-images"
    gallery_name = "gal_avd"
    image_name = "avd_w11_new"
    image_version = "1.0.0"
    replication_regions = ["WestEurope"]
    storage_account_type = "Standard_LRS"
}
  managed_image_name                = "myPackerImage1"
  managed_image_resource_group_name = "myPackerGroup"
  os_type                           = "Windows"
  subscription_id                   = ""
  tenant_id                         = ""
  vm_size                           = "Standard_D4s_v5"
  winrm_insecure                    = true
  winrm_timeout                     = "5m"
  winrm_use_ssl                     = true
  winrm_username                    = "packer"
}

Varma 1,495

HI Martin, I have tried template you have given , here is the template with my resource details but coming with e error as below

Error: Error: 1 error(s) occurred:

Specify either a VHD (image_url), Image Reference (image_publisher, image_offer, image_sku), a Managed Disk (custom_managed_disk_image_name, custom_managed_disk_resource_group_name), or a Shared Gallery Image (shared_image_gallery) on windows.pkr.hcl line 11: (source code not available) Please suggest

packer {
required_plugins {
   azure = {
     version = ">= 1.0.0"
     source = "github.com/hashicorp/azure"
   }
 }
}


source "azure-arm" "example" {
 # Using Azure CLI for authentication
 use_azure_cli_auth = true 
 location = "eastus2"
image_offer     = "WindowsServer"
 image_publisher = "MicrosoftWindowsServer"
 image_sku       = "2016-Datacenter"
 os_type         = "Windows"
 vm_size         = "Standard_NV6ads_A10_v5"
 os_disk_size_gb = 64

 shared_image_gallery {
   resource_group       = "cg"
 
   gallery_name         = "gallery1"
   image_name           = "webserver"
   image_version        = "1.0.0"
     subscription = "93048f2d-2d0f-44cc-b12c-4df25a3c5ff5"
 }
  
 shared_image_gallery_destination {
   resource_group       = "cg"
 
   gallery_name         = "gallery1"
   image_name           = "webserver"
   image_version        = "1.0.1"
   replication_regions  = ["eastus2"]
   storage_account_type = "Standard_LRS"
 }
}
build {
 sources = [
   "source.azure-arm.example"
 ]
 provisioner "powershell" {
   inline = [
     "Remove-WindowsFeature Web-Server",
     "while ((Get-Service RdAgent).Status -ne 'Running') { Start-Sleep -s 5 }",
     "while ((Get-Service WindowsAzureGuestAgent).Status -ne 'Running') { Start-Sleep -s 5 }",
     "& $env:SystemRoot\\System32\\Sysprep\\Sysprep.exe /oobe /generalize /quiet /quit",
     "while($true) { $imageState = Get-ItemProperty HKLM:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Setup\\State | Select ImageState; if($imageState.ImageState -ne 'IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE') { Write-Output $imageState.ImageState; Start-Sleep -s 10  } else { break } }"
   ]
 }
}

Could you please suggest further,

we have given source and detaination as part of computer gallery, that is clear

image is coming from source in the source compute gallery

and published imaged gets pushed in to the destination with new image in the gallert

then why managed image? could you please suggest what exactly need to add and why need to add?

Looking forword for your response.

Thank you

Martin Therkelsen 1,410 MVP

You have both a image source and a gallery source in your code. Try this instead.

packer {
  required_plugins {
    azure = {
      version = ">= 1.0.0"
      source = "github.com/hashicorp/azure"
    }
  }
} 
  
source "azure-arm" "example" {
  # Using Azure CLI for authentication
  use_azure_cli_auth = true 
  location = "eastus2"
  
  shared_image_gallery {
    resource_group       = "cg"   
    gallery_name         = "gallery1"
    image_name           = "webserver"
    image_version        = "1.0.0"
    subscription = "93048f2d-2d0f-44cc-b12c-4df25a3c5ff5"
  }
    
  shared_image_gallery_destination {
    resource_group       = "cg"   
    gallery_name         = "gallery1"
    image_name           = "webserver"
    image_version        = "1.0.1"
    replication_regions  = ["eastus2"]
    storage_account_type = "Standard_LRS"
  }
}
build {
  sources = [
  "source.azure-arm.example"
  ]
  provisioner "powershell" {
    inline = [
    "Remove-WindowsFeature Web-Server",
    "while ((Get-Service RdAgent).Status -ne 'Running') { Start-Sleep -s 5 }",
    "while ((Get-Service WindowsAzureGuestAgent).Status -ne 'Running') { Start-Sleep -s 5 }",
    "& $env:SystemRoot\\System32\\Sysprep\\Sysprep.exe /oobe /generalize /quiet /quit",
    "while($true) { $imageState = Get-ItemProperty HKLM:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Setup\\State | Select ImageState; if($imageState.ImageState -ne 'IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE') { Write-Output $imageState.ImageState; Start-Sleep -s 10  } else { break } }"
    ]
  }
}

Varma 1,495

HI Martin I have tried above template, but coming up with quota error, I have raised support ticket to increase the quota 1. is there any way that we can fix quota error promptly?


Build 'azure-arm.example' errored after 2 minutes 55 seconds: deployments.DeploymentsClient#Validate: Failure sending request: StatusCode=0 -- Original Error: Code="InvalidTemplateDeployment" Message="The template deployment failed with error: 'The resource with id: '/subscriptions/93048f2d-2d0f-44cc-b12c-4df25a3c5ff5/resourceGroups/pkr-Resource-Group-in4ixwmuwb/providers/Microsoft.Compute/virtualMachines/pkrvmin4ixwmuwb' failed validation with message: 'The requested size for resource '/subscriptions/93048f2d-2d0f-44cc-b12c-4df25a3c5ff5/resourceGroups/pkr-Resource-Group-in4ixwmuwb/providers/Microsoft.Compute/virtualMachines/pkrvmin4ixwmuwb' is currently not available in location 'eastus2' zones '' for subscription '93048f2d-2d0f-44cc-b12c-4df25a3c5ff5'. Please try another size or deploy to a different location or zones. See https://aka.ms/azureskunotavailable for details.'.'." Details=[{"code":"SkuNotAvailable","message":"The resource with id: '/subscriptions/93048f2d-2d0f-44cc-b12c-4df25a3c5ff5/resourceGroups/pkr-Resource-Group-in4ixwmuwb/providers/Microsoft.Compute/virtualMachines/pkrvmin4ixwmuwb' failed validation with message: 'The requested size for resource '/subscriptions/93048f2d-2d0f-44cc-b12c-4df25a3c5ff5/resourceGroups/pkr-Resource-Group-in4ixwmuwb/providers/Microsoft.Compute/virtualMachines/pkrvmin4ixwmuwb' is currently not available in location 'eastus2' zones '' for subscription '93048f2d-2d0f-44cc-b12c-4df25a3c5ff5'. Please try another size or deploy to a different location or zones. See https://aka.ms/azureskunotavailable for details.'."}]

First I will try template with source and destination as computer gallery and then parllely I would like to test with fresh image also, for that can you please suggest what exactly I should amend in the above latest template? Thank you for your help, Looking Forword to hear from you.

Martin Therkelsen 1,410 MVP

Often you can raise the quota yourself. You can try by going to the subscription and then click "Usage + quotas" and then find the SKU you are trying to use. See the picture below as well for guidance. User's image

If you want to create a fresh image instead of using gallery as a source, you can use the code below.

{
    "builders": [
        {
            "type": "azure-arm",
            "client_id": "",
            "client_secret": "",
            "tenant_id": "",
            "subscription_id": "",
            "managed_image_resource_group_name": "myPackerGroup",
            "managed_image_name": "myPackerImage",
            "image_publisher": "MicrosoftWindowsServer",
            "image_offer": "WindowsServer",
            "image_sku": "2016-Datacenter",

            "shared_image_gallery_destination": {
                "subscription": "",
                "resource_group": "rg-avd-images",
                "gallery_name": "gal_avd",
                "image_name": "avd_w11_new",
                "image_version": "1.0.0",
                "replication_regions": [ "WestEurope" ],
                "storage_account_type": "Standard_LRS"
            },
            "build_resource_group_name": "myPackerGroup",
            "os_type": "Windows",
            "vm_size": "Standard_D4s_v5",
            "winrm_insecure": true,
            "winrm_timeout": "5m",
            "winrm_use_ssl": true,
            "winrm_username": "packer"
        }
    ]
}

Varma 1,495 Reputation points

2024-02-09T07:36:20.17+00:00

HI Martin, Thank you In the below highlighted yellow color,

1. I believe both managed image resource group and managed image name both should be already available in the Azure, before I execute the template , am I correct? Could please clarify If yes, in my scenario what is the way Forword to proceed creating managed image? I believe if i know answers for this I am close to preparing and finalizing the template
Martin Therkelsen 1,410 Reputation points MVP

2024-02-09T07:43:33.3+00:00

Yes, in this scenario, the resource group must already exist in Azure.
Varma 1,495 Reputation points

2024-02-09T07:45:37.9233333+00:00

But what about managed image, does packer will create in the backend? or we need to make sure managed image already in place in the resource group?
Martin Therkelsen 1,410 Reputation points MVP

2024-02-09T07:48:08.8733333+00:00

No, the managed image will be the output, so you don't need to do anything there. The Compute Gallery should exist, and it should have the image definition as well, but you are also using that as a source, so I assume that is OK already.
Martin Therkelsen 1,410 Reputation points MVP

2024-02-09T07:48:44.9066667+00:00

I have run the packer build in my azure with only the resource group and compute gallery in place.
Varma 1,495 Reputation points

2024-02-09T07:56:41.9+00:00
So input for the managed image is gallery 1.0.0 version as highlighted below, am I correct?

here below are both outputs then:

one is gallery image version (1.0.0) and then packer uses that apply softwares and then it produces managed image which is second output

hope this statement is correct?
Martin Therkelsen 1,410 Reputation points MVP

2024-02-09T08:06:11.65+00:00

In the image you just pasted you are using a fresh image and putting a new version into the image gallery. You are putting it in as version 1.0.0, which I would say is wrong, since you probably have a version 1.0.0 already. The destination version needs to be a new item and not reuse. I often use dates a version numbers instead of 1.0.0, this could be like this: 20240209.07.00
Varma 1,495 Reputation points

2024-02-09T08:11:06.2066667+00:00

HI Martin I agree, Yes 1.0.0. is already there but just for example I am mentioning okay lets assume 1.0.1 ( we kept in in the shared destination gallery section ) and then that new image version 1.0.1 will be the input to the managed image and with that managed image will created and managed image will be come output, am I correct?
kobulloc-MSFT 26,801 Reputation points Microsoft Employee Moderator

2024-02-09T08:20:31.32+00:00
Hello again, @Varma ! I'm going to include this here for tracking in the conversation. Thank you for your interest in Packer but please remember to follow the Microsoft Q&A guidelines when asking questions:

Avoid posting multiple questions in a single thread: Multiple questions makes it difficult for other community members who are looking for solutions as well as for members who are trying to help answer your question. Please create separate threads for each of your questions.
Martin Therkelsen 1,410 Reputation points MVP

2024-02-09T08:22:15.0233333+00:00

Not quite. The managed image is different from an image in the compute gallery. The above output will be a managed image (An azure resource) and a new version in the compute gallery. You can delete that part if you don't need the managed image.
Varma 1,495 Reputation points

2024-02-09T08:27:15+00:00

@kobulloc msft You can remove all other questions if anything is there as I dont see any response over there, you can make this one as active, thank you, noted
Martin Therkelsen 1,410 Reputation points MVP

2024-02-09T08:36:24.3733333+00:00

I think it is because you ask many questions inside this single question. You asked for the code for using Compute Gallery as a source. I provided that for you. Now you are asking for an explanation of the packer code itself and the Azure resources it is creating. I don't mind it, but it is actually multiple questions in a single Q&A question.
Varma 1,495 Reputation points

2024-02-09T08:41:11.37+00:00

HI Martin, I got the point, but since you know the background I am asking again, and there is less chance to get response from others on this unique requirement. IF I feel new question is need defiantly I will raise it
Martin Therkelsen 1,410 Reputation points MVP

2024-02-09T08:47:42.54+00:00

As said, I don't mind it :)
Varma 1,495 Reputation points

2024-02-09T08:57:11.2333333+00:00

Thank you :) Coming to Deleting managed image, you mean deleting it from portal after creation, am I correct?

Martin Therkelsen 1,410 MVP

Updated templates.

For fresh image use this:

{
    "builders": [
        {
            "type": "azure-arm",
            "client_id": "",
            "client_secret": "",
            "tenant_id": "",
            "subscription_id": "",
            "image_publisher": "MicrosoftWindowsServer",
            "image_offer": "WindowsServer",
            "image_sku": "2016-Datacenter",
            "shared_image_gallery_destination": {
                "subscription": "",
                "resource_group": "rg-avd-images",
                "gallery_name": "gal_avd",
                "image_name": "avd_w11_new",
                "image_version": "1.0.0",
                "replication_regions": [ "WestEurope" ],
                "storage_account_type": "Standard_LRS"
            },
            "build_resource_group_name": "myPackerGroup",
            "os_type": "Windows",
            "vm_size": "Standard_D4s_v5",
            "winrm_insecure": true,
            "winrm_timeout": "5m",
            "winrm_use_ssl": true,
            "winrm_username": "packer"
        }
    ]
}

To use compute gallery as source, you can use this:

{
    "builders": [
        {
            "type": "azure-arm",
            "client_id": "",
            "client_secret": "",
            "tenant_id": "",
            "subscription_id": "",
            "shared_image_gallery": {
                "subscription": "",
                "resource_group": "rg-avd-images",
                "gallery_name": "gal_avd",
                "image_name": "avd_w11",
                "image_version": "1.0.0"
            },
            "shared_image_gallery_destination": {
                "subscription": "",
                "resource_group": "rg-avd-images",
                "gallery_name": "gal_avd",
                "image_name": "avd_w11_new",
                "image_version": "1.0.0",
                "replication_regions": ["WestEurope"],
                "storage_account_type": "Standard_LRS"
            },
            "build_resource_group_name": "myPackerGroup",
            "os_type": "Windows",
            "vm_size": "Standard_D4s_v5",
            "winrm_insecure": true,
            "winrm_timeout": "5m",
            "winrm_use_ssl": true,
            "winrm_username": "packer",
            "communicator": "winrm"
        }
    ]    
}

Varma 1,495 Reputation points

2024-02-09T10:10:14.86+00:00

test123

Share via

Where we define source image and destination image details while automating the image creation using packer

0 additional answers

Your answer