I have a fairly simple Unix shell script packaged up in an Alpine Linux Docker container hosted on an Azure container registry. A VM runs this script with cron:

docker login <snip>
docker pull example.com/bar:latest
docker run  example.com/bar:latest

Can I do without the VM and use Azure services instead, perhaps with some sort of scheduler running this on an Azure Container Instance?

My motivation is not wanting to maintain and pay for the VM.


Azure Container Instances (ACI) may be a good option as you suggest. These let you run a container directly on Azure, without having to manage a VM, with per-second billing for the time the container is used.

Although one of the demos on that blog mentions Kubernetes, the idea of ACI is that you can create a container through the Azure CLI with az container create, just like on your local workstation with docker create.

To create the container, you can use Azure CLI (az command, see quick start docs) or Azure Cloud Shell.

You would need to create/run the container on a schedule from somewhere else - Azure Functions might be a good place to run the "container create" command from a scheduled function. This supports bash, PowerShell, and other languages - all running on Windows.

If you want to keep using Docker containers without running VMs or learning Kubernetes, this might be a good option.

Alternatively, you could move all your code into Azure Functions, but that's a bigger decision.

Update: Jan 2019 - Azure Logic Apps can be used to run scheduled tasks as well.

  • I wasn't aware I could use PowerShell or Bash for Azure Functions! Thanks – Sijmen Mulder Jul 30 '17 at 12:12
  • Yes, you can run any executable from Azure Functions, and bash is explicitly mentioned in this overview doc. To call PowerShell modules, see this blog. – RichVel Jul 31 '17 at 5:51
  • It’s common to use cloud functions such as Azure Functions, AWS Lambda etc to run installation scripts that configure cloud services (e.g, setup a new cloud environment). So you can expect all serverless services and frameworks to support running bash or similar. Traditionally the first VM you would setup was a “control host” server to use as the place to run all setup of all environments. Going Serverless to run all such scripts means no host to pay for. A control server if hacked leaks a map of your environments, old scripts and possibly cached passwords. Serverless bash is more secure. – simbo1905 Jan 4 at 6:55

For an alternative approach, I would investigate Azure functions:

No VM continually running.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.