Azure Container Instance stuck in "Waiting"

Francesca Argenziano 20 Reputation points



I’m trying to deploy an Azure Container Instance with Qdrant linked to a storage account through ­the following command in the azure CLI on Windows:

az container create 
--resource-group ResourceGroupName
--name qdrant-aci 
--image qdrant/qdrant:master 
--ports 6333 
--cpu 4 
--memory 1 
--vnet qdrant-vnet 
--subnet qdrant-subnet 
--ip-address Private 
--azure-file-volume-share-name qdrantshare 
--azure-file-volume-account-name qdrantstorageaccount 
--azure-file-volume-account-key $STORAGE_KEY 
--azure-file-volume-mount-path "/qdrant/storage"

The ACI is stuck on “Waiting” status even if the storage account exists and it’s in the same subnet.

User's image

Any ideas on how to troubleshoot?

Azure Container Instances
Azure Container Instances
An Azure service that provides customers with a serverless container experience.
663 questions
Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,845 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. deherman-MSFT 34,691 Reputation points Microsoft Employee

    @Francesca Argenziano

    I just tested and was able to successfully create an Azure Container Instances using the image qdrant/qdrant:master I also was able to successfully mount Azure Files during the creation. Since it worked for me without issue, I suspect it might have something to do with your Azure Files configuration of Storage Account.

    Try creating a new Storage Account following the tutorial here. Check the settings of your storage account and make sure there is nothing blocking ACI from using it. You can also try checking az container show --resource-group myResourceGroup --name mycontainer to get diagnostic information.

    Hope this helps! If you are still facing issues with your container please let me know and we can troubleshoot with you directly.

    If you still have questions, please let us know in the "comments" and we would be happy to help you. Comment is the fastest way of notifying the experts.

    If the answer has been helpful, we appreciate hearing from you and would love to help others who may have the same question. Accepting answers helps increase visibility of this question for other members of the Microsoft Q&A community.

    Thank you for helping to improve Microsoft Q&A!

    User's image

    0 comments No comments

  2. Francesca Argenziano 20 Reputation points

    Thank you for the answer! The problem was that I was running this command on Command Prompt rather than Bash so I had to use %STORAGE_KEY% instead of $STORAGE_KEY.

    0 comments No comments

  3. deherman-MSFT 34,691 Reputation points Microsoft Employee

    @Francesca Argenziano

    I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

    Issue: Your Container Instance was stuck deploying when utilizing Azure File Share mounting

    Solution: Since you were using Azure CLI in Command prompt you needed to modify the way to store variables. %STORAGE_KEY% instead of $STORAGE_KEY

    If you have any other questions or are still running into more issues, please let me know. Thank you again for your time and patience throughout this issue.

    Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

    0 comments No comments