Container Instance suddenly stop while doing npm install, is there a limit in storage?

Question

I created a container instance via Azure CLI. When this container starts, I run a shell script that copies files from a mounted Azure file share. Afterward, I extract a zip file into a directory to execute 'npm install' and a Sencha build. Following this, I archive the build output and copy it back to the mounted Azure file share. The reason for performing these copy and operations within the container is that when I do this via a mounted directory, it takes too much time. Is there a storage limit for a container, or do you have another solution for this scenario? I'm open to recommendations. Thank you.

Answer 1

There is a storage limit, which is generally 50GB - and can be seen here : https://learn.microsoft.com/en-us/azure/container-instances/container-instances-resource-and-quota-limits#standard-container-resources

It sounds like you're building an app, which i'd typically do during my CI/CD pipeline. I'd typically create the container image as part of that process then store it in an Azure Container Registry. This way if I wanted to run the web app on an ACI, then i'd just pull that container. I appreciated that i've guessed your scenario, so apologies if your actual scenario is a little different.