No, at this time we only support the default Docker for Azure VHD.
Not at this time, but it is on our roadmap for future releases.
Docker for Azure should work with all supported Azure Marketplace regions.
All container logs are aggregated within the
xxxxlog storage account.
Send an email to email@example.com or post to the Docker for Azure GitHub repositories.
In Azure, if your resource group is misbehaving, please run the following diagnostic tool from one of the managers - this will collect your docker logs and send them to Docker:
$ docker-diagnose OK hostname=manager1 OK hostname=worker1 OK hostname=worker2 Done requesting diagnostics. Your diagnostics session ID is 1234567890-xxxxxxxxxxxxxx Please provide this session ID to the maintainer debugging your issue.
Note: Your output will be slightly different from the above, depending on your swarm configuration.
Docker for Azure sends anonymized minimal metrics to Docker (heartbeat). These metrics are used to monitor adoption and are critical to improve Docker for Azure.
By default when you SSH into a manager, you will be logged in as the regular username:
docker - It is possible however to run commands with elevated privileges by using
For example to ping one of the nodes, after finding its IP via the Azure/Azure portal (e.g. 10.0.0.4), you could run:
$ sudo ping 10.0.0.4
Note: Access to Docker for Azure and Azure happens through a shell container that itself runs on Docker.
All regions can be found here: Microsoft Azure Regions An exerpt of the above regions to use when you create your service principal are:
australiaeast australiasoutheast brazilsouth canadacentral canadaeast centralindia centralus eastasia eastus eastus2 japaneast japanwest northcentralus northeurope southcentralus southeastasia southindia uksouth ukwest westcentralus westeurope westindia westus westus2