# Limited memory in ACI for running Node-Red Dashboard nodes

**URL:** <https://discourse.nodered.org/t/limited-memory-in-aci-for-running-node-red-dashboard-nodes/39092>\
**Category:** General\
**Created:** [13 January 2021 21:26 UTC](https://discourse.nodered.org/t/limited-memory-in-aci-for-running-node-red-dashboard-nodes/39092 "2021-01-13T21:26:26Z")\
**Posts on this page:** 5\
**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:** [13 January 2021 21:26 UTC](https://discourse.nodered.org/t/limited-memory-in-aci-for-running-node-red-dashboard-nodes/39092/1 "2021-01-13T21:26:26Z")

</div>

This question is very much related to my previous question on running Node-Red in an ACI.  
([Deployed flow in Azure Container Instances disappears](https://discourse.nodered.org/t/deployed-flow-in-azure-container-instances-disappears/34618/6))

I am now able to deploy Node-Red to any ACI, and having the deployed flow saved using Azure File Share as a mapped Docker volume. Using Docker Integration Azure CLI I did it using a command like:

docker run -p 1880:1880 -v demobundlestorageaccount/nr-test-volume:/data --domainname iotdemobundle --name noderedinstance nodered/node-red

using the demobundlestorageaccount storage account with the file share nr-test-volume in it.

The Node-Red instance then runs as intended on port 1880.

The problem occurs when I try to download dashboard nodes using the Palette Manager.

When trying to install node-red-dashboard, the install chews away and then returns an error.

It seems like the node/container/x is lacking memory, which is weird since the max ACI size is 15 GB (as I understand it). This is part of the log:

2020-12-22T23:34:51.318Z [err] nospc  
2020-12-22T23:34:51.318Z [err] ENOTSUP: operation not supported on socket, symlink '../mime/cli.js' -\> '/data/node\_modules/.bin/mime'  
2020-12-22T23:34:51.318Z [err] npm  
2020-12-22T23:34:51.318Z [err]  
2020-12-22T23:34:51.318Z [err] ERR!  
2020-12-22T23:34:51.318Z [err]  
2020-12-22T23:34:51.318Z [err] nospc  
2020-12-22T23:34:51.319Z [err] There appears to be insufficient space on your system to finish.  
2020-12-22T23:34:51.319Z [err] npm  
2020-12-22T23:34:51.319Z [err]  
2020-12-22T23:34:51.319Z [err] ERR!  
2020-12-22T23:34:51.319Z [err]  
2020-12-22T23:34:51.319Z [err] nospc  
2020-12-22T23:34:51.319Z [err] Clear up some disk space and try again.  
2020-12-22T23:34:51.420Z [err]  
2020-12-22T23:34:51.420Z [err] npm  
2020-12-22T23:34:51.421Z [err]  
2020-12-22T23:34:51.421Z [err] ERR!  
2020-12-22T23:34:51.421Z [err] A complete log of this run can be found in:  
2020-12-22T23:34:51.421Z [err] npm  
2020-12-22T23:34:51.421Z [err]  
2020-12-22T23:34:51.421Z [err] ERR!  
2020-12-22T23:34:51.421Z [err] /data/.npm/\_logs/2020-12-22T23\_34\_51\_322Z-debug.log  
2020-12-22T23:34:51.429Z rc=161

Do you have any idea on why this occurs and how to remedy it?

Grateful for all comments on the matter.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [13 January 2021 21:34 UTC](https://discourse.nodered.org/t/limited-memory-in-aci-for-running-node-red-dashboard-nodes/39092/2 "2021-01-13T21:34:09Z")

</div>

It isn't memory that you are lacking but the ability to add to the filing system I think. Are you sure that the `/data` filing system is actually writable?

---

<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:** [13 January 2021 21:48 UTC](https://discourse.nodered.org/t/limited-memory-in-aci-for-running-node-red-dashboard-nodes/39092/3 "2021-01-13T21:48:59Z")

</div>

Not 100%.

It seems like the flows are persisted, they were still there after a full restart of the ACI.  
Without the managed volume they would have been swiped, right?

But, anyway, I guess I should check the Azure Storage Account folders somehow?

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [13 January 2021 21:53 UTC](https://discourse.nodered.org/t/limited-memory-in-aci-for-running-node-red-dashboard-nodes/39092/4 "2021-01-13T21:53:18Z")

</div>

The neverending "fun" that is Docker 🙂

---

<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:** [14 March 2021 21:53 UTC](https://discourse.nodered.org/t/limited-memory-in-aci-for-running-node-red-dashboard-nodes/39092/5 "2021-03-14T21:53:22Z")

</div>

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