2

I keep reading that Azure Container Instances can be "spun up in seconds". However, my tests have shown that even the simplest (smallest) containers are taking around 45 secs to launch. Is this typical? This container launches on my desktop pretty much instantly.

I have an Alpine/Nginx image with a single static file. About 100Mb. It's hosted in the Azure Container Registry in East Coast 2 with Premium SKU. When I create a container based on this (also in East Coast 2) via the portal is takes around 45 secs before it reports that the container is ready.

Is there something I am doing wrong here? Does doing it interactively via the portal add 40 secs or something?

45 secs is technically seconds, but this is a minimal container and it's getting close to a minute, so, not really what I was expecting.

dommer
  • 378

1 Answers1

3

It's all going to come down to your container image size. On your desktop your caching the image, so it runs instantly. ACI, is stateless so it will not cache your image, each time you launch an instance it has to download it from the repo.

Take a look at the size of your image, see if you can reduce it. If you launch an ACI instance with just a minimal alpine container it will be faster.

Sam Cogan
  • 39,089