This repository contains examples and CI/CD pipelines to build custom images for Microsoft DevBox.
Config
Factory
Schemas
Scripts
Templates
Artifacts
Local Development & Build
Every folder named xxxBox represents a custom image for Microsoft DevBox. The folder contains the following files:
The image.json file is the main configuration file for the image. Here you can find an example or template for the image.json file.
A DevDrive can be mounted into a DevBox. It uses not NTFS but ReFS to improve performance. click for more information
Files and directory inside of this folder are copied to the Packer VM before any package of pre/post script is executed. Please be careful with large files. Communication to the Packer VM is using WinRM which is not a high speed tool when it comes to copying files (especially larger ones). more
In case you need to upload large files to the Packer VM please rely on the resolve artifacts feature of this build pipeline. Instead of placing a large artifact file in this folder use a Windows shortcut, pointing to the download URL of the file. The name of the Windows shortcut file (plus the default extension '.url' for Windows shortcuts) must contain the name of the file after downloading.
largefile.zip.url --> [download] --> largefile.zip
Resolving these shortcut files will happen after the artifacts upload.
The same approach used for large size artifacts can be used to download sensitive files stored within a Azure KeyVault as BASE64 encoded secret. Use the secret identifier as the target URL of the Windows shortcut file.
In _schemas you can find the JSON schema files for the image.json, aliases, defaults, factory and general definitions.
In _artifacts you can find a devbox.bgi. A .bgi (BgInfo Configuration File) file keeps track of computer configuration information and stores custom settings chosen by the user