All docker machines on azure are created with the same storage account.

[NatashaHull]

My team recently had an issue where one of our storage accounts went down and that took out all of the docker machines in a given resource group. We want the additional functionality to have different storage accounts per docker machine in a given resource group, as Microsoft has recommended to us, to avoid this issue in the future. Whether this would involve being able to name the created/used storage account within a given resource group or just say create a new one when creating a new machine does not particularly matter.

[benc-uk]

Wow, open since March and no response? Is anyone looking at these? A much, much better approach would be for the Azure driver to use managed disks for the VM https://docs.microsoft.com/en-gb/azure/virtual-machines/windows/managed-disks-overview. This is now the recommended way. Creating a storage account is not the best way to do this anymore

[NatashaHull]

@benc-uk thank you for getting back to me. When this issue was filed, docker-machine didn't support using managed disks because they were so new. The team switched to using the azure container service with docker swarm and managed disks not long after this issue was filed.

[Dean-Christian-Armada]

@NatashaHull , what is the command to create VMs with managed disks?

I'm trying to create a VM on a managed "availability set"

docker-machine create --driver azure \ --azure-subscription-id 123456 example \ --azure-location eastasia \ --azure-resource-group docker-premium-disk \ --azure-storage-type Premium_LRS \ --azure-open-port 80 \ --azure-open-port 8000 \ --azure-open-port 8001 \ --azure-open-port 8002 \ --azure-size Standard_DS11_v2 \ --engine-storage-driver overlay2 \ managed-disk-node-1

But got this error instead

Error creating machine: Error in driver during machine creation: compute.VirtualMachinesClient#CreateOrUpdate: Failure responding to request: StatusCode=409 -- Original Error: autorest/azure: Service returned an error. Status=409 Code="OperationNotAllowed" Message="Addition of a VM with managed disks to non-managed Availability Set or addition of a VM with blob based disks to managed Availability Set is not supported. Please create an Availability Set with 'Aligned' SKU in order to add a VM with managed disks to it."

[ps23]

Add something like: --azure-availability-set="${hostname}-as"