Skip to content
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

Closed
khowling opened this issue Sep 10, 2018 · 16 comments · Fixed by #10465
Closed

az webapp create doesnt support using a acr image #7261

khowling opened this issue Sep 10, 2018 · 16 comments · Fixed by #10465
Labels
App Services az appservice H2-2019 Features to be finished by the second half of 2019 Service Attention This issue is responsible by Azure service team.
Milestone

Comments

@khowling
Copy link

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

@ahmedelnably
Copy link
Contributor

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

@yugangw-msft yugangw-msft added Web Apps az webapp and removed Web Apps labels Sep 12, 2018
@mcwienczek
Copy link

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

@markheath
Copy link
Contributor

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

@panchagnula
Copy link
Contributor

@yiliaomsft & @Nking92 can you look at this request

@SindreOsnes
Copy link

+1 from me as well. This is really needed.

@yiliaomsft
Copy link

We're looking into it.

@panchagnula
Copy link
Contributor

CC: //@apwestgarth for windows containers

@WilliamMortlMicrosoft
Copy link

this is needed as soon as possible for Microsoft engagements with other companies (I'm an employee in CSE)

@panchagnula panchagnula modified the milestones: Sprint 67, Sprint 66 Jul 16, 2019
@panchagnula panchagnula modified the milestones: Sprint 66, Sprint 67 Jul 26, 2019
@yugangw-msft yugangw-msft removed the App Services az appservice label Aug 1, 2019
@panchagnula panchagnula modified the milestones: Sprint 67, Sprint 68 Aug 8, 2019
@yonzhan yonzhan modified the milestones: Sprint 68, Sprint 69 Aug 19, 2019
@btardif
Copy link
Member

btardif commented Aug 19, 2019

We are on track for s69

@yonzhan yonzhan modified the milestones: Sprint 73, Sprint 74 Sep 8, 2019
@panchagnula
Copy link
Contributor

This has been fixed.

@haroldrandom haroldrandom added App Services az appservice Feature H2-2019 Features to be finished by the second half of 2019 Service Attention This issue is responsible by Azure service team. labels Oct 25, 2019
@tsgenge
Copy link

tsgenge commented Jan 22, 2020

Using az webapp create using an ACR image still returns "Access is denied. Not authorized. latest". Is this in production now? Even using the Azure CLI shell in the portal (therefore latest) gives the same error.

@tsgenge
Copy link

tsgenge commented Jan 23, 2020

Using az webapp create using an ACR image still returns "Access is denied. Not authorized. latest". Is this in production now? Even using the Azure CLI shell in the portal (therefore latest) gives the same error.

It works today, but in an odd way. I assume it was an outage, though I have switched to linux containers / service plan. I noticed that it still doesn't connect using the ACR option - inspecting the app service created its connecting using a "private repository" connecting using my ACR access tokens.

@nkemakolam
Copy link

I tried creating a web app for container I used the -i option yet it didn’t give me acr as a default container reg instead it treated my parameter as a private container repo.where as i supplied my acr url and image name to the command.please any idea.??????

@mjdall
Copy link

mjdall commented Nov 22, 2020

I tried creating a web app for container I used the -i option yet it didn’t give me acr as a default container reg instead it treated my parameter as a private container repo.where as i supplied my acr url and image name to the command.please any idea.??????

I had this issue when my ACR url didn't start with https://. Setting with https:// registered it as a container registry instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
App Services az appservice H2-2019 Features to be finished by the second half of 2019 Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

Successfully merging a pull request may close this issue.