New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

`az webapp create` doesnt support using a acr image #7261

khowling opened this Issue Sep 10, 2018 · 3 comments


None yet
6 participants

khowling commented Sep 10, 2018

Describe the bug
az webapp create can only create a webapp using a public dockerhub or built in image, it doesnt support passing in registry credentials for a acr image.

I'm trying to create a webapp based on a image in acr, but I cannot pass in the registry credentials into the create command. So I need to first create the webapp with a random public container, then run the az webapp config container set command that accepts registry credentials

To Reproduce
run az webapp create --deployment-container-image-name no way of passing in registry credentials

Expected behavior
I'd like to see consistency between the command line options for az webapp create --deployment-container-image-name and az webapp config container set --docker-custom-image-name

Environment summary
Bash on Windows


This comment has been minimized.


ahmedelnably commented Sep 10, 2018

We have it on our backlog and will update the thread once we finish the work, that's said we don't have an ETA to share right now


This comment has been minimized.

mcwienczek commented Oct 6, 2018

+1 for this, could be useful for us as well


This comment has been minimized.


markheath commented Oct 19, 2018

Also, if you have a container that needs certain environment variables set, there is no obvious way to create the webapp with the app settings. you have to first do az webapp create and then az webapp config appsettings set.

Would be nice to be able to create a new webapp from ACR and with environment variables correctly configured in a single step

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment