aci: accessing private docker registry on non-standard port with ACI

[yugangw-msft]

Ported from user feedback.

az container create\
        --name testcontainer\
        --resource-group test-rg
        --image private.example.com:5000/dockerimage:build94\
        --ports 80\
        --ip-address Private\
        --registry-login-server private.example.com:5000\
        --registry-username reguser\
        --registry-password ***

fails with an error of The server 'private.example.com:5000' in the 'imageRegistryCredentials' of container group 'testcontainer' is invalid. It should be a valid host name without protocol

Linked issue at ACR was closed as we determined the issue is no longer ACR related.

//cc: @kawaja //cc: @mmacy, @neilpeterson, @seanmck @dlepow

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc

[dlepow]

Including ACI PMs: /cc: @dkkapur, @macolso

[RavirahulPadmanabhan]

I'm also facing this issue. We have an old registry running on port 5000. And now due to this issue/limitation with Azure CLI, we have to expose the registry on 443 and change everywhere.

[dyllan-to-you]

Any update on this?

I have no trouble using Azure App Services with my private container registry. It looks like the issue is with the serverside validation of the template's imageRegistryCredentials property. I encounter the same issue when trying to create an ACI via the web portal.

[NBroomfield]

+1 This is causing me issues trying to access a private GitLab CI repository on default port of 5050.

[alessap]

Any update on this issue?

[joshuaswickirl]

I can't believe that this is still an issue.

[devops4you90]

Is ACI PM sleeping? No one responding on this

[devops4you90]

@yugangw-msft can you check this with msft pg?

[kennethgp]

ACI does not support private registries other than ACR (via Trusted Services), and ACR doesn't support custom port. It makes no sense to support adding colon to login server input.