Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

Latest commit

 

History

History
33 lines (27 loc) · 1.79 KB

custom-images.md

File metadata and controls

33 lines (27 loc) · 1.79 KB
Raw

Fuzzing using Custom OS Images

In order to use custom OS images in OneFuzz, the image must run the Azure VM Agent.

Building custom images can be automated using the Linux or Windows image builders for Azure.

If you have a custom Windows VHD, you should follow the Guide to prepare a VHD for Azure.

From there, rather than using Image SKUs such as Canonical:0001-com-ubuntu-server-focal:20_04-lts:latest, use the full resource ID for the shared image. Supported ID formats are:

  • VM image:
    /subscriptions/{subscription}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/images/{image}
  • gallery image (latest):
    /subscriptions/{subscription}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{gallery}/images/{image}
  • gallery image (specific version):
    /subscriptions/{subscription}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{gallery}/images/{image}/versions/{version}
  • shared gallery image (latest):
    /subscriptions/{subscription}/providers/Microsoft.Compute/locations/{location}/sharedGalleries/{gallery}/images/{image},
  • shared gallery image (specific version):
    /subscriptions/{subscription}/providers/Microsoft.Compute/locations/{location}/sharedGalleries/{gallery}/images/{image}/versions/{version}

The Service Principal for the OneFuzz instance must have RBAC to the image sufficient to read and deploy the images, and the image must be replicated into the region of the scaleset.