Cannot use "storage account" and "file share" that I have created, while doing &-CodePudding

The

Now if I log into "az" CLI like so :

az login

I see my subscription "shapeShopResourceGroup"

{ "id": "/subscriptions/8cdb50cb-ede8-4eac-80df-55afadf861cd/resourceGroups/shapeShopResourceGroup", "location": "eastus", "managedBy": null, "name": "shapeShopResourceGroup", "properties": { "provisioningState": "Succeeded" }, "tags": null, "type": "Microsoft.Resources/resourceGroups" },

I am also using the "aci" context :

However when I do docker compose up I get this error :

error: The storage account named shapeshopstorageaccount is already taken.

This is really frustrating to me because, yes, shapeshopstorageaccount DOES EXIST! I created it for ME!

So then, I think somehow my context does not associate properly with my subscription. So to check I type in :

az storage account list

...and my shapeshopstorageaccount is listed in the returned JSON. So it seems like the association between my storage account and subscription exists.

Why is azure (or docker-compose) not associating the declared volume in my YML file with the azure storage that I created??

CodePudding user response：

I think that storage account must be unique globally. The reason for that is that the name becomes part of the URL, let's say https://shapeshopstorageaccount.blob.core.windows.net

Try to add oliver_s0mthing to your storage account,probably that is unique name.

CodePudding user response：

You might need to login to Azure Container Registry with az acr login --name <acrName> and from the same terminal run the compose command. Check this for more details.

Alternatively, you might need to include the storage account key in yaml, like this.

Check also this, in which I am not sure why variable names are different though.