Azure-docs: Usage error when creating web app in app service plan

[Simon-HL]

When creating a Web App in step 2. of "Host the web app in App Service", the az cli command fails and returns a usage error.

az webapp create -n <your web app name> -g <your resource group name> -p <your app service plan name> --deployment-local-git
usage error: --runtime | --deployment-container-image-name | --multicontainer-config-type TYPE --multicontainer-config-file FILE

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 681e10a1-05d3-5761-2afd-42602a7efecf
• Version Independent ID: f72e21b1-3530-8554-f1f1-fc66b222a485
• Content: Real-time data visualization of your IoT hub data in a web app
• Content Source: articles/iot-hub/iot-hub-live-data-visualization-in-web-apps.md
• Service: iot-hub
• GitHub Login: @robinsh
• Microsoft Alias: robinsh

[Mike-Ubezzi-MSFT]

@Simon-HL Thank you for bringing this to our attention. We will step through this tutorial, identify the root cause and update the document accordingly.

[Mike-Ubezzi-MSFT]

@Simon-HL The issue appears to be that there is an issue with the container or access to the container. Was the following step followed: Download the web app from GitHub:

git clone https://github.com/Azure-Samples/web-apps-node-iot-hub-data-visualization.git
cd web-apps-node-iot-hub-data-visualization

All the following steps in the tutorial are completed in the following directory: web-apps-node-iot-hub-data-visualization

Now, when you go to run the az cli command to create the webapp, my assumption here is that you should be in the same directory where the above was downloaded to:

az webapp create -n <your web app name> -g <your resource group name> -p <your app service plan name> --deployment-local-git

Is this what is occurring in your case or are there additional parameters required, such as:

--runtime
--deployment-container-image-name
--multicontainer-config-type TYPE
--multicontainer-config-file FILE

In looking at az webapp create, it appears that the documentation may need to be updated.

az webapp create --name
--plan
--resource-group
[--deployment-container-image-name]
[--deployment-local-git]
[--deployment-source-branch]
[--deployment-source-url]
[--docker-registry-server-password]
[--docker-registry-server-user]
[--multicontainer-config-file]
[--multicontainer-config-type {COMPOSE, KUBE}]
[--runtime]
[--startup-file]
[--subscription]
[--tags]

[Mike-Ubezzi-MSFT]

@robinsh There is an issue with this tutorial in that Step 2 of the Host the webapp in App Service, the az cli command is expecting some additional parameters:

Step 2:
az webapp create -n <your web app name> -g <your resource group name> -p <your app service plan name> --deployment-local-git

is looking for the following additional parameters:

--runtime
--deployment-container-image-name
--multicontainer-config-type TYPE
--multicontainer-config-file FILE

[JimacoMS3]

reassign JimacoMS3

[robinsh]

@JimacoMS3 I'm writing that down for future reference!

[JimacoMS3]

@Mike-Ubezzi-MSFT @Simon-HL Can you try including the runtime parameter in the command? Specifically "node|10.6"? (or greater) as in the following command:

az webapp create -n <your web app name> -g <your resource group name> -p <your app service plan name> -r "node|10.6" --deployment-local-git

Please let me know if that works.

[Mike-Ubezzi-MSFT]

@Simon-HL Can you update this issue with the result of implementing -r "node|10.6" in step 2 as detailed in the previous comment. This will be helpful.

[Simon-HL]

@Mike-Ubezzi-MSFT @Simon-HL Can you try including the runtime parameter in the command? Specifically "node|10.6"? (or greater) as in the following command:

az webapp create -n <your web app name> -g <your resource group name> -p <your app service plan name> -r "node|10.6" --deployment-local-git

Please let me know if that works.

That worked

[JimacoMS3]

@Simon-HL Thanks again for your help on this! FYI a fix to the topic has been merged into our private repo and will go live this afternoon. @Mike-Ubezzi-MSFT FYI.