# Node-Red running in Azure Container Instances

**URL:** <https://discourse.nodered.org/t/node-red-running-in-azure-container-instances/28154>\
**Category:** General\
**Created:** [11 June 2020 07:07 UTC](https://discourse.nodered.org/t/node-red-running-in-azure-container-instances/28154 "2020-06-11T07:07:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tobiaspe](https://avatars.discourse-cdn.com/v4/letter/t/8edcca/32.png) [@tobiaspe](https://discourse.nodered.org/u/tobiaspe)\
**Post date:** [11 June 2020 07:07 UTC](https://discourse.nodered.org/t/node-red-running-in-azure-container-instances/28154/1 "2020-06-11T07:07:34Z")

</div>

I am trying to deploy Node-Red in the easiest way possible to a Docker container.

I have tried starting a Docker container and pulling an Node-Red image from Docker Hub on my local machine which works fine. I can then access Node-Red on 127.0.0.1:1880.

What I am aiming to do is to run Node-Red under Azure Container Instances, i.e. deploy a Node-Red container serverlessly. An Azure Container Instance is intended to be very easy to get started with and provide a public DNS name to access the service.

I followed the Quickstart steps under [https://docs.microsoft.com/en-us/azure/container-instances/container-instances-quickstart](https://docs.microsoft.com/en-us/azure/container-instances/container-instances-quickstart) in great detail. The container was indeed stood up and the logs states the expected:

11 Jun 06:46:53 - [info] Node-RED version: v1.0.6  
11 Jun 06:46:53 - [info] Node.js version: v10.20.1  
11 Jun 06:46:53 - [info] Linux 4.15.0-1083-azure x64 LE  
11 Jun 06:46:53 - [info] Loading palette nodes  
11 Jun 06:46:54 - [info] Settings file : /data/settings.js  
11 Jun 06:46:54 - [info] Context store : 'default' [module=memory]  
11 Jun 06:46:54 - [info] User directory : /data  
11 Jun 06:46:54 - [warn] Projects disabled : editorTheme.projects.enabled=false  
11 Jun 06:46:54 - [info] Flows file : /data/flows.json  
11 Jun 06:46:54 - [info] Creating new flow file  
11 Jun 06:46:54 - [warn]

* * *

Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials  
file will not be recoverable, you will have to delete it and re-enter  
your credentials.

## You should set your own key using the 'credentialSecret' option in your settings file. Node-RED will then re-encrypt your credentials file using your chosen key the next time you deploy a change.

11 Jun 06:46:54 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/)  
11 Jun 06:46:54 - [info] Starting flows  
11 Jun 06:46:54 - [info] Started flows

When I try to access the Node-Red instance on the public DNS nothing happens. Am I missing some container-to-host mapping of ports? How can I update the container configuration to be accessible?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [10 August 2020 07:07 UTC](https://discourse.nodered.org/t/node-red-running-in-azure-container-instances/28154/2 "2020-08-10T07:07:41Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.