Michael Friis

Docker for Azure Public Beta

Michael Friis

Last week Docker for AWS went public beta, and today Docker for Azure reached the same milestone and is ready for public testing. Docker for Azure is a great way for ops to setup and maintain secure and scalable Docker deployments on Azure.

Docker for Azure

With Docker for Azure, IT ops teams can:

  • Deploy a standard Docker platform to ensure teams can seamlessly move apps from developer laptops to Dockerized staging and production environments, without risk of incompatibilities or lock-in.
  • Integrate deeply with underlying infrastructure to ensure Docker takes advantage of the host environment’s native capabilities and exposes a familiar interface to administrators.
  • Deploy the platform to all the places where you want to run Dockerized apps, simply and efficiently
  • Make sure the latest and greatest Docker versions are available for the hardware, OSs, and infrastructure you love, and provide solid upgrade paths from one Docker version to the next.

To try the latest Docker for Azure beta based on the latest Docker Engine betas, click the button below or get more details on the beta site:

Installation takes a few minutes, and will give you a fully functioning swarm, ready to deploy and scale Dockerized apps.

We first unveiled the Docker for Azure private beta on stage at DockerCon 2016 back in June, and we are excited to be opening up to beta to the public. We received lots of great feedback from private beta testers (thanks!) and incorporated as much of it as possible. Enhancements added during the private beta include:

  • All container logs are stored in an Azure storage account for later retrieval and inspection. That means you no longer have to rummage around on hosts to find the error you’re looking for or worry that logs are lost if a worker is replaced.
  • Built-in diagnose tool lets you submit a swarm-wide diagnostic dump to Docker so that we can help diagnose and troubleshoot a misbehaving Docker for Azure swarm.
  • Improved upgrade stability so that you can confidently upgrade your Docker for Azure to the latest version

We’re particularly proud of the progress we’ve made on diagnostics and upgradability. These are features that set a true production system apart from simple fire-and-forget templates that just spin up resources without thought for debugging or future upgrades.

The improvements added during the private beta complement the initial features Docker for Azure launched with earlier this year:

  • Simple access and management using SSH
  • Quick and secure deployment of websites thanks to auto-provisioned and auto-configured load balancers
  • Secure and easy-to-manage Azure network and instance configuration

With today’s public beta announcement, we hope to get even more users interested in running Docker on Azure and testing the beta. Check out the detailed docs and sign up on beta.docker.com to be notified of updates and new beta versions.

Docker for AWS and Azure currently only support Linux-based swarms of managers and workers. Windows Server worker support will come as Docker on Windows Server matures. If you have questions or feedback, send an email or post to the Docker for AWS or the Docker for Azure forums.

Additional Resources

Continue reading...


3 thoughts on “Docker for Azure Public Beta

  1. I just tried it out, but I got a timeout during deployment:

    TRACKING ID3e1ab86f-2e00-4c70-85bb-efec57cb085d
    TIMESTAMP12/14/2016, 4:51:19 PM
    DURATION18 minutes 5 seconds
    RESOURCE ID/subscriptions/XXX/resourceGroups/docker4azure/providers/Microsoft.Compute/virtualMachineScaleSets/swarm-worker-vmss
    "error": {
    "code": "ServerTimeout",
    "message": "The request timed out. Diagnostic information: timestamp '20161214T155118Z', subscription id 'XXX', tracking id 'fa129d55-1031-4da1-a034-11eeac9f476c', request correlation id 'd9a9e739-0776-40ad-a32b-e1f2544d4e3e'."

    Same for "swarm-manager-vmss"

    • That looks like an Azure error – could you try again or open an issue with Azure?

      • It works now, thank you! But I have a new question: When I look at my swarm-worker-scaleset, under "Scaling", it is NOT possible to scale worker instance count up and down? Why?

        I like to use the feature of adding or deleting VMs in a "classic" environemnt and of course the autoscale feature on CPU load (automatically start/stop VMs). It looks like this isn't possible in "Docker for Azure" – so this prevents me from using it in production =(

Leave a Reply