You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Learn how to create a template to use with Azure Image Builder.
4
4
author: danis
5
5
ms.author: danis
6
-
ms.date: 03/20/2020
6
+
ms.date: 01/23/2020
7
7
ms.topic: article
8
8
ms.service: virtual-machines-linux
9
9
ms.subservice: imaging
@@ -91,7 +91,7 @@ By default, Image Builder will not change the size of the image, it will use the
91
91
```
92
92
93
93
## vnetConfig
94
-
If you do not specify any VNET properties, then Image Builder will create its own VNET, Public IP, and NSG. The Public IP is used for the service to communicate with the build VM, however if you do not want a Public IP or want Image Builder to have access to your existing VNET resources, such as configuration servers (DSC, Chef, Puppet, Ansible), file shares etc, then you can specify a VNET. For more information, review the [networking documentation](https://github.com/danielsollondon/azvmimagebuilder/blob/master/aibNetworking.md#networking-with-azure-vm-image-builder), this is optional.
94
+
If you do not specify any VNET properties, then Image Builder will create its own VNET, Public IP, and NSG. The Public IP is used for the service to communicate with the build VM, however if you do not want a Public IP or want Image Builder to have access to your existing VNET resources, such as configuration servers (DSC, Chef, Puppet, Ansible), file shares etc., then you can specify a VNET. For more information, review the [networking documentation](./../aibNetworking.md), this is optional.
95
95
96
96
```json
97
97
"vnetConfig": {
@@ -149,9 +149,9 @@ The API requires a 'SourceType' that defines the source for the image build, cur
149
149
- SharedImageVersion - this is used when you are using an image version in a Shared Image Gallery as the source.
150
150
151
151
### ISO source
152
-
We are deprecating this functionality from image builder, as there are now [RHEL Bring Your Own Subscription images](https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/redhat/byos), please review the timelines below:
153
-
* 31st March 2020 - Image Templates with RHEL ISO sources will now longer be accepted by the resource provider.
154
-
* 30th April 2020- Image Templates that contain RHEL ISO sources will not be processed any more.
152
+
We are deprecating this functionality from image builder, as there are now [RHEL Bring Your Own Subscription images](https://docs.microsoft.com/azure/virtual-machines/workloads/redhat/byos), please review the timelines below:
153
+
* 31 March 2020 - Image Templates with RHEL ISO sources will now longer be accepted by the resource provider.
154
+
* 30 April 2020- Image Templates that contain RHEL ISO sources will not be processed anymore.
155
155
156
156
### PlatformImage source
157
157
Azure Image Builder supports Windows Server and client, and Linux Azure Marketplace images, see [here](https://docs.microsoft.com/azure/virtual-machines/windows/image-builder-overview#os-support) for the full list.
@@ -210,7 +210,7 @@ By default, the Image Builder will run for 240 minutes. After that, it will time
210
210
[ERROR] complete: 'context deadline exceeded'
211
211
```
212
212
213
-
If you do not specify a buildTimeoutInMinutes value, or set it to 0, is will use the default value. You can increase or decrease the value, up to the maximum of 960mins (16hrs). For Windows, we do not recommend setting this below 60 minutes. If you find you are hitting the timeout, review the [logs](https://github.com/danielsollondon/azvmimagebuilder/blob/master/troubleshootingaib.md#collecting-and-reviewing-aib-image-build-logs), to see if the customization step is waiting on something like user input.
213
+
If you do not specify a buildTimeoutInMinutes value, or set it to 0, this will use the default value. You can increase or decrease the value, up to the maximum of 960mins (16hrs). For Windows, we do not recommend setting this below 60 minutes. If you find you are hitting the timeout, review the [logs](https://github.com/danielsollondon/azvmimagebuilder/blob/master/troubleshootingaib.md#collecting-and-reviewing-aib-image-build-logs), to see if the customization step is waiting on something like user input.
214
214
215
215
If you find you need more time for customizations to complete, set this to what you think you need, with a little overhead. But, do not set it too high because you might have to wait for it to timeout before seeing an error.
216
216
@@ -404,7 +404,7 @@ OS support: Windows
404
404
405
405
Customize properties:
406
406
- **type** – WindowsUpdate.
407
-
- **searchCriteria** - Optional, defines which type of updates are installed (Recommended, Important etc), BrowseOnly=0 and IsInstalled=0 (Recommended) is the default.
407
+
- **searchCriteria** - Optional, defines which type of updates are installed (Recommended, Important etc.), BrowseOnly=0 and IsInstalled=0 (Recommended) is the default.
408
408
- **filters** – Optional, allows you to specify a filter to include or exclude updates.
409
409
- **updateLimit** – Optional, defines how many updates can be installed, default 1000.
410
410
@@ -415,7 +415,7 @@ By default, Azure Image Builder will also run ‘deprovision’ code at the end
415
415
416
416
The commands Image Builder users to generalize may not be suitable for every situation, so Azure Image Builder will allow you to customize this command, if needed.
417
417
418
-
If you are migrating existing customization, and you are using different Sysprep/waagent commands, you can using the Image Builder generic commands, and if the VM creation fails, use your own Sysprep or waagent commands.
418
+
If you are migrating existing customization, and you are using different Sysprep/waagent commands, you can use the Image Builder generic commands, and if the VM creation fails, use your own Sysprep or waagent commands.
419
419
420
420
If Azure Image Builder creates a Windows custom image successfully, and you create a VM from it, then find that the VM creation fails or does not complete successfully, you will need to review the Windows Server Sysprep documentation or raise a support request with the Windows Server Sysprep Customer Services Support team, who can troubleshoot and advise on the correct Sysprep usage.
0 commit comments