Microsoft Azure Container Instances
Containers are quickly becoming the preferred way to package, deploy, and manage cloud applications. Azure Container Instances offers the fastest and simplest way to run a container in Azure, without having to provision any virtual machines and without having to adopt a higher-level service. Azure Container Instances is a great solution for any scenario that can operate in isolated containers, including simple applications, task automation, and build jobs. For scenarios where you need full container orchestration, including service discovery across multiple containers, automatic scaling, and coordinated application upgrades, I recommend the Azure Container Service.
Here you see a quick example of making a Microsoft Azure Container Instance :
You can create an Microsoft Azure Container Instance with the Azure Portal or with Azure Cloud Shell (CLI 2.0)
From the Azure portal, you will create the Azure Container Instance Name, Container Image, Resource Group and Location.
For this quick example I used the public Docker HUB Image WordPress ( https://hub.docker.com/r/library/wordpress/)
Here you set the configuration of the Azure Container Instance, like how many Cores and Memory for the Container.
and Public IP Address yes or no with the port settings.
When you are almost finished in 3 steps, don’t hit OK but have a look at Download Template and Parameters first.
From here you can :
- Download the Template for making Automation deployment scripts.
- Save the template to the Library
- And Deploy the script button.
Also have a look here !
It’s really powerful to work with Azure Resource Management Templates.
Deploying the Azure Container Instance with WordPress
Done, just click here to see the running Container Instance
When you go to the IP-Address of the Azure Container Instance with your browser, you will see the WordPress site config.
Of course you can do this installation also from the Azure Cloud Shell :
Here you find an Overview of Microsoft Azure Cloud Shell and the Activation
Azure Cloud Shell is a browser-based shell experience to manage and develop Azure resources. Cloud Shell offers a browser-accessible, pre-configured shell experience for managing Azure resources without the overhead of installing, versioning, and maintaining a machine yourself. Cloud Shell provisions machines on a per-request basis and as a result machine state will not persist across sessions. Since Cloud Shell is built for interactive sessions, shells automatically terminate after 20 minutes of shell inactivity.
Bash in Cloud Shell
Tools
| Category | Name |
|---|---|
| Linux shell interpreter | Bash sh |
| Azure tools | Azure CLI 2.0 and 1.0 AzCopy Batch Shipyard |
| Text editors | vim nano emacs |
| Source control | git |
| Build tools | make maven npm pip |
| Containers | Docker CLI/Docker Machine Kubectl Draft DC/OS CLI |
| Databases | MySQL client PostgreSql client sqlcmd Utility mssql-scripter |
| Other | iPython Client Cloud Foundry CLI |
Language support
| Language | Version |
|---|---|
| .NET | 1.01 |
| Go | 1.7 |
| Java | 1.8 |
| Node.js | 6.9.4 |
| Python | 2.7 and 3.5 (default) |
Secure automatic authentication
Cloud Shell securely and automatically authenticates account access for the Azure CLI 2.0.
Azure Files persistence
Since Cloud Shell is allocated on a per-request basis using a temporary machine, files outside of your $Home and machine state are not persisted across sessions. To persist files across sessions, Cloud Shell walks you through attaching an Azure file share on first launch. Once completed Cloud Shell will automatically attach your storage for all future sessions.
Learn more about attaching Azure file shares to Cloud Shell.
Here you see in Azure Cloud Shell the Azure Container Instance (ACI)
See here more information about Microsoft Azure Container Instances
Hope this is helpful for you to start with Containers, here you can follow the Cloud Container Community
