Table of Contents
- Webhooks from Docker Hub
- Using the Azure Go SDK to update container groups
- See it in action
- Final Thoughts
Back in July, Microsoft announced Azure Container Instances, a new Azure service delivering containers with great simplicity and speed and without any Virtual Machine infrastructure to manage. ACIs are the fastest and easiest way to run a container in the cloud.
Essentially, this allowed you to run single or multi-container groups (scheduled on the same host machine, within the same local network, storage and lifetime) with fast startup times, hypervisor-level security, public IP address connectivity and billing by the second.
One thing that Azure Container Instances didn’t have when first launched was the ability to update the image of a container while keeping the public IP address of the container group - essentially, when you had a new version / tag of your image, you had to redeploy the everything and you would have gotten a different public IP address.
Here we are only talking about using ACI without any orchestrator - you can use ACI with Kubernetes through the aci-connector-k8s project, or through the new virtual-kubelet, which creates a virtual node in your Kubernetes cluster that schedules pods on top of Azure Container Instances.
In this article we will not use any of the two projects mentioned, but build a simple app that listens for webhooks from Docker Hub (or any other container registry) and uses the Azure Go SDK to update the container.
Please note that while you will not be able to do this from the portal, it can be done through the Azure REST API or various language SDKs.
Webhooks from Docker Hub
As I was saying earlier, we will accept incoming webhooks from Docker Hub and update the Azure containers accordingly. First let’s see how a Docker Hub webhook looks like:
Essentially, in the webhook data we have all necessary information to update the container with the newly pushed image.
Now taking that JSON and using it with this little cool utility that generates Go structs from JSON, we get the Go struct that contains the webhook data:
You can find the project on GitHub
From this point, we’ll create a simple web server that listens for webhook requests and will update the container using the Go SDK.
Using the Azure Go SDK to update container groups
In order to use the Azure Go SDK you need some credentials - first of all, go through the documentation showing you how to create a service principal.
You will need the following:
AZURE_TENANT_ID: contains your Azure Active Directory tenant ID or domain AZURE_SUBSCRIPTION_ID: contains your Azure Subscription ID AZURE_CLIENT_ID: contains your Azure Active Directory Application Client ID AZURE_CLIENT_SECRET: contains your Azure Active Directory Application Secret
The credentials above allow us to programatically access Azure resources through the REST API or through an SDK - in our case, we’ll use the Go SDK - they are used as environment variables in the program, together with the resource group name and container group name:
RESOURCE_GROUP_NAME: the name of the resource group where the container group is deployed CONTAINER_GROUP_NAME: name of the container group
If you use
vndras dependency manager for Go, check the
vndr.conffile for this project - otherwise, add
github.com/Azure/azure-sdk-for-goto your project, or simply clone this repo which contains the entire application.
First, we need an instance of
Here we simply use the SDK to authenticate using the credentials we got earlier and retrieve a new instance of
This is the standard procedure to authenticate the Go SDK to your Azure subscription and you can use it to create other types of clients.
Then, we iterate through the desired container group, searching for the container with the same image as the one in the webhook, then update it:
Because you can have multiple containers in your group, we need to iterate through all of them to find the one with the image from the webhook. When we find it, we set the image to be the newly received from the webhook and call
All you have to do now is read the body of the HTTP request containing the webhook and execute the function:
See it in action
First of all, we need to depoy an Azure Container Instance based on an image (we own) from Docker Hub:
We give it a name, an image and a resource group:
Now we can setup the OS type, resources (CPU and memory) and the public IP address:
After a few moments, you should have a running container with a public IP address:
This is the container running:
Now we need to:
- start the web server that accepts webhooks from Docker Hub
- setup the webhook from Docker Hub to push to our web server
- update the Docker image and have our container updated
Don’t forget to add the environment variables for the Azure credentials and the resource group and container group name!
I will use ngrok to expose my local webserver to accept webhooks from Docker Hub - in another article we will see another way to run our function that updates the container group.
The webserver from the repo listens on port 8080 by default (you can change it) - so I will start a tunnel to my local port 8080 through:
ngrok http 8080:
Then, I’ll setup the Docker Hub webhook to push to the public endpoint exposed by
Now let’s see what happens when we
docker push radumatei/aci-hooks:v2 to Docker Hub:
Our webserver gets called and starts executing the container update method:
The container in the portal gets automatically updated:
Our container is actually updated to the new version (notice the public IP address is unchanged):
Of course, we can deploy this application to Azure Container Instance - Inception!
This app was quickly put together to show that using the SDK you can update Azure Container Instances using webhooks from Docker Hub - of course, it can be extended to take webhooks from your favourite container registry, and even keep track of multiple ACI instances to update - this is outside the scope of the article.
Hopefully in a future article we will see how to stop using
ngrok and a full web server and move towards serverless - Azure Functions.
Please note that while the container gets updated, your app will be down for a couple of seconds!
Thanks for reading! If you want to extend the functionality of this little tool, you are welcome to contribute on GitHub with issues and pull requests.
I would love to hear your thoughts - feel free to comment below, or send me an email