Each time I start a new container, the image is pulled from the repository. Even if I start 10 times the same image. I would like to have the image cached (maybe on the resource group level) so that I only get the penalty of pull once.169 votes
When an ACI container exits normally and the restart-policy is Never you should automatically delete the ACI. Currently it sticks around with a status of Terminated.
In my scenario I want to spin up ACI's to drain an Azure queue. When the queue is empty my ACI workers will exit and I do not want to have to go and clean up the ACI remnants afterwards. They should cleanly remove themselves as if they never existed.
This can be an option if there are scenarios where this is undesirable.84 votes
Current memory sizes are too small for my usage.
I need something to start quickly, load a 1-50GB dataset - process it in memory for half an hour and deallocate.27 votes
Please comment with specific CPU/GB needs as input.
Only allowing for 5 ports to be open on a container is very limiting. Please let us open at least 8 if not no limit.14 votes
Shares from Azure Files are mounted in directories accessible only to the "root" user. If the container is configured to run its application as a non-root user, the entrypoint has to become a shell script that can assign appropriate permissions to the share directory. Running a script to chmod/chown every file on the share is very slow.
It would be much easier to use shares from Azure Files if there was a way to control what user the share was mounted for.7 votes
- Don't see your idea?