Tuesdays with Corey: Debian GNU/Linux and Azure Container Service

Corey Sanders, Director of Program Management on the Microsoft Azure Compute team announces the NEW release of Debian image in our Marketplace as well as walking us through the Azure Container Service and where to sign up to get started.

Don’t forget – we’re always looking for Suggestions and Questions here in the comments section OR via twitter #AzureTwC. You never know – you might make it to an upcoming episode and be a virtual star of the show – like THIS one!

Post any questions, topic ideas or general conversation here in the comments OR online on via Twitter.

About author View all posts

Rick

4 CommentsLeave a comment

    • When deploying your service you can choose either Docker Swarm or Apache Mesos with Marathon as the orchestrator/framework for your containers. You use the standard API for the chosen orchestration technology. So for Docker Swarm you would use `docker ps`, for Maraton/Mesos you would use either the UI or the REST API. Of course, you can also use any other tools capable of talking to these orchestrators.

      • I’m sorry I guess I worded my question poorly. I didn’t mean list my personal containers.

        I mean get my container listed in the marketplace. I work on the Rocket.Chat project. We have an official trusted image, we’d like to get listed so that others can easily deploy our platform to Azure like they can with many other services.

        • Oh I see. Microsoft does not provide a Docker registry, we have a partnership with Docker that means we will be caching images from the official Docker Hub. This means that all you need to do is publish to Docker Hub.

          However, you appear to be asking about getting your application listed in the Marketplace. You can find information about this process at https://azure.microsoft.com/en-us/marketplace/partner-program/


Warning: sizeof(): Parameter must be an array or an object that implements Countable in D:\home\site\wwwroot\wp-content\plugins\projectnami-blob-cache\project-nami-blob-cache.php on line 416

Fatal error: Uncaught WindowsAzure\Common\ServiceException: Fail: Code: 400 Value: The account being accessed does not support http. details (if any): <?xml version="1.0" encoding="utf-8"?><Error><Code>AccountRequiresHttps</Code><Message>The account being accessed does not support http. RequestId:e9d287b8-a01e-0051-19ec-89d6ba000000 Time:2021-08-05T11:27:45.9074952Z</Message><AccountName>ritgcache</AccountName></Error>. in D:\home\site\wwwroot\wp-content\plugins\projectnami-blob-cache\library\WindowsAzure\Common\Internal\Http\HttpClient.php:382 Stack trace: #0 D:\home\site\wwwroot\wp-content\plugins\projectnami-blob-cache\library\WindowsAzure\Common\Internal\Http\HttpClient.php(275): WindowsAzure\Common\Internal\Http\HttpClient::throwIfError(400, 'The account bei...', '\xEF\xBB\xBF<?xml versio...', Array) #1 D:\home\site\wwwroot\wp-content\plugins\projectnami-blob-cache\library\WindowsAzure\Common\Internal\RestProxy.php(141): WindowsAzure\Common\Internal\Http\HttpClient->send(Array, Object(WindowsAzure\Common\Internal\ in D:\home\site\wwwroot\wp-content\plugins\projectnami-blob-cache\library\WindowsAzure\Common\Internal\Http\HttpClient.php on line 382