I can't get IP or FQDN for my container

jose Guerrero 0 Reputation points
2024-09-23T17:11:17.98+00:00

Dear Sirs.

After creating a container in Azure to contain the Node-RED application, I am unable to obtain the IP or FQDN to launch the application in the browser.

Could you tell me how I can obtain this data?

Thanks in advance.

Note: the first time I created a container I got these datas at first time, but after deleting the container, I'm not able to get it again.

Azure Container Registry
Azure Container Registry
An Azure service that provides a registry of Docker and Open Container Initiative images.
455 questions
Azure Container Instances
Azure Container Instances
An Azure service that provides customers with a serverless container experience.
700 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Sai Krishna Katakam 345 Reputation points Microsoft Vendor
    2024-09-23T21:05:35.8266667+00:00

    Hi jose Guerrero,

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

    To obtain the IP or FQDN for your Azure container running the Node-RED application, please follow these troubleshooting steps.

    • Check the Container Status make sure the container is running. You can do this from the Azure Portal or by using the Azure CLI:
    az container show --resource-group <your-resource-group> --name <your-container-name> --query "{IP:ipAddress.ip, FQDN:ipAddress.fqdn}" --output table
    
    • When creating or recreating the container, make sure it has a public IP and a DNS name label. This is essential for accessing it externally. You can specify the DNS name label when creating the container like this:
    az container create \
         --resource-group <your-resource-group> \
         --name <your-container-name> \
         --image <your-image> \
         --dns-name-label <your-dns-label> \
         --ports 1880
    
      The DNS label must be globally unique, and once it's added, you can access the container at `http://<your-dns-label>.<region>.azurecontainer.io`.
    
    • If you deployed the container into a Virtual Network (VNet), it might only have a private IP, meaning it’s not accessible externally. Ensure that the container is set up for public access if needed.
    • When you delete a container, its public IP and DNS label may be released. Make sure to reconfigure them when recreating the container.

    For more information, please refer to this document: Deploy a container group with custom DNS settings, Networking in Azure Container Apps environment. Create a container image for deployment to Azure Container Instances.

    If you have any further queries, do let us know. If the comment is helpful, please click "Upvote".


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.