Hi there, following the provided documentation on az webapp create I'm not able to create a webapp without specifying any of:
--runtime
--deployment-container-image-name
--multicontainer-config-type TYPE
--multicontainer-config-file FILE
Running az webapp create -g anygrouppreviouslycreated -n test -p anyplanpreviouscreated leads to the following output:
usage error: --runtime | --deployment-container-image-name | --multicontainer-config-type TYPE --multicontainer-config-file FILE
I suspect it has to do with the --is-linux flag while creating the service plan.
It's also very disappointing that using --docker-custom-image-name is not available which would allow me to do the webapp creation and image instantiation via ACR in one command. With the current issue, I have to basically deploy any available image from docker hub and replace it right after with az webapp container set to reference the actual container to be used from ACR.
Version info:
azure-cli (2.0.43)
Related:
https://github.com/MicrosoftDocs/azure-docs/issues/6286
https://github.com/MicrosoftDocs/azure-docs/issues/11145
Thanks!
did you manage to solve this issue?
I find this issue whenever we try to develop using Linux Service Plan
I could create webapp from web-cli using windows.
@rijdz No, unfortunately not as this is clearly an issue with the CLI. I worked around it for now by running the commonly used hello-world image which immediately exits. I then use az webapp config container set to replace it with my custom docker image from ACR.
same issue here with the latest az cli 2.0.4.9, workaround by @elsesiy is working thankfully for a demo app
same issue here, while exactly following this tutorial : https://azure.microsoft.com/en-ca/resources/videos/deploy-a-spring-boot-app-to-azure/
Unfortunately for Linux apps these are required for the Docker container apps we have plans to support an extra parameter - being tracked by this https://github.com/Azure/azure-cli/issues/7261
@panchagnula The issue you're referencing describe the exact same issue but was filed a month later. Not sure what's the point in closing this one?
This is still not fixed years later? Wow.
I received the same error and no details even with --verbose switch. And the duped issue is not related 
Most helpful comment
@rijdz No, unfortunately not as this is clearly an issue with the CLI. I worked around it for now by running the commonly used hello-world image which immediately exits. I then use
az webapp config container setto replace it with my custom docker image from ACR.