Issue with Missing IP address/FQDN when provisioning ACI through portal

Informatics For Life 55

As the title indicates: While using Azure Container Instances (ACI) on the portal to run a container (docker or another source), the container is deployed fine, but, it does not have a public IP address or a DNS name (even though one was specified). I found this issue mentioned a while back, so not sure if there is a workaround (while using the portal) or if I am missing something.

Nikhil Duserla 2,180 Reputation points Microsoft Vendor

2024-09-25T02:37:21.23+00:00

Hi @Informatics For Life,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

We understand from your query that you are experiencing an issue where the container deployed using Azure Container Instances (ACI) on the portal does not have a public IP address or a DNS name.

I have tried deploying with PowerShell, and it's working for me. Please attempt to deploy using PowerShell as well.

az container create --resource-group <resource-group-name> --name <your-container-name> --image mcr.microsoft.com/azuredocs/aci-helloworld --dns-name-label <your-dns-label> --ports 80

If you have any further queries, do let us know.
Andy Lau Pik Hui 65 Reputation points

2024-09-25T08:30:29.3633333+00:00

@Informatics For Life I'm now facing this same error when deploying ACI from Azure Portal. Have you solve this?
Zbigniew Wyszomierski 0 Reputation points

2024-09-25T14:29:07.9766667+00:00

Same issue to me, ACI can't be created using Portal
Zbigniew Wyszomierski 0 Reputation points

2024-09-25T14:40:15.2866667+00:00

I can observe the same error via Portal
Conrad Wilson 0 Reputation points

2024-09-25T15:04:04.33+00:00

I have encountered the same problem. Thanks for the AZ CLI suggestion! Put me out of my misery...
Oliver Brinker 0 Reputation points

2024-09-25T15:32:43.1766667+00:00

Same for me. The way over the CLI works, creating it in the portal the IP address and FQDN are missing.
Informatics For Life 55 Reputation points

2024-09-25T15:38:38.1166667+00:00

Thanks for the comments. Is this a reported bug with the portal, and is there an ETA to fix it?

I tried the CLI suggestion, but, it's giving me an internal server error. Attached screenshot. Let me know if I am missing something.

Screenshot 2024-09-25 113112.jpg
Michael Bear 20 Reputation points

2024-09-28T21:04:40.72+00:00

I too am seeing this issue.

I'll go the AZ CLI route too, but jeesh things should just work... ;-) Edit: I managed to work up a solution. I needed more command options and detailed them in my Q&A post.

https://video2.skills-academy.com/en-us/answers/questions/2083328/fqdn-not-shown-for-azure-container-instance?orderby=helpful

Accepted answer

Nikhil Duserla 2,180 Reputation points Microsoft Vendor

2024-09-26T10:23:29.3333333+00:00

Hi Informatics For Life,

Thank you for sharing your information.

Please switch to PowerShell and try with the same.

If you have any further queries, do let us know.

If the answer provides a solution for you, please click "Accept Answer" and "Upvote it."
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Issue with Missing IP address/FQDN when provisioning ACI through portal

0 additional answers

Your answer