I can't get IP or FQDN for my container

jose Guerrero 5

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.

Sai Krishna Katakam 1,510 Reputation points Microsoft Vendor

2024-09-24T21:54:21.5733333+00:00

Hi jose Guerrero,

Just checking in to see if you had a chance to review my comment on your question. Please let us know if it was helpful and feel free to reach out if you have any further queries.

If you found the information useful, please click "Upvote" on the post to let us know.

Thank You.
Sai Krishna Katakam 1,510 Reputation points Microsoft Vendor

2024-09-25T18:05:14.0766667+00:00

Hi jose Guerrero,

I wanted to check if you had the opportunity to review the information which was provided in my previous posted comment.

If it was helpful, please click "Upvote" on his post to let us know.

Thank You.
Ransingh Satyajit Ray 0 Reputation points

2024-10-12T14:06:58.99+00:00

I am facing similar problem. The very first time I created I was getting the IP and FQDN but after deleting I am not getting the same, both are empty.

1 answer

Sai Krishna Katakam 1,510 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".
Please sign in to rate this answer.
jose Guerrero 5 Reputation points

2024-09-29T18:01:08.4133333+00:00

Thank you very much for your help.

I managed to create a new container even easier than I did.

However, I have noticed that the flows I create are not saved, not even the palettes I install in the container. Every time I go back to Node-RED in the container, it starts without saving any changes.

What should I do to make the changes persist in the container?

Thanks in advance.

Sai Krishna Katakam 1,510 Reputation points Microsoft Vendor

2024-09-30T03:42:24.0666667+00:00

Hi jose Guerrero,

The reason your changes (flows and installed palettes) are not being saved is that containers are ephemeral by design. This means any changes you make inside the container will be lost when it restarts or is recreated.

To make your changes persist, you can mount an external volume, such as an Azure File Share, to store your Node-RED data outside the container. Here’s how you can do it:

Create an Azure File Share in an Azure Storage Account. This will store your Node-RED data.

Mount the File Share to the container when you create it. Use the following command to do this with the Azure CLI:

az container create \ --resource-group <your-resource-group> \ --name <your-container-name> \ --image <your-node-red-image> \ --dns-name-label <your-dns-label> \ --ports 1880 \ --azure-file-volume-account-name <your-storage-account-name> \ --azure-file-volume-account-key <your-storage-account-key> \ --azure-file-volume-share-name <your-file-share-name> \ --azure-file-volume-mount-path /data

The /data path is where Node-RED stores its flows and configuration. By mounting the file share to this path, your data will be saved even if the container is restarted.

You can find more details in the Azure Container Instances - Persistent Storage documentation.

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

Sai Krishna Katakam 1,510 Reputation points Microsoft Vendor

2024-10-01T01:30:39.7933333+00:00

Hi jose Guerrero,

Just checking in to see if you had a chance to review my comment on your question. Please let us know if it was helpful and feel free to reach out if you have any further queries.

If you found the information useful, please click "Accept Answer" and "Upvote" on the post to let us know.

Thank You.

Sai Krishna Katakam 1,510 Reputation points Microsoft Vendor

2024-10-14T07:48:28.69+00:00

Hi jose Guerrero,

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."
Sign in to comment

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

Share via

I can't get IP or FQDN for my container

1 answer

Your answer