# Trouble with Docker, Nodered@1.0.4 & Dashboard@2.19.4

**URL:** <https://discourse.nodered.org/t/trouble-with-docker-nodered-1-0-4-dashboard-2-19-4/23930>\
**Category:** Dashboard\
**Created:** [30 March 2020 23:23 UTC](https://discourse.nodered.org/t/trouble-with-docker-nodered-1-0-4-dashboard-2-19-4/23930 "2020-03-30T23:23:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mozz164](https://avatars.discourse-cdn.com/v4/letter/m/ecc23a/32.png) [@Mozz164](https://discourse.nodered.org/u/Mozz164)\
**Post date:** [30 March 2020 23:23 UTC](https://discourse.nodered.org/t/trouble-with-docker-nodered-1-0-4-dashboard-2-19-4/23930/1 "2020-03-30T23:23:41Z")

</div>

Hi, I'm having a problem that I've been trying to solve for a few days now....but cannot seem to get anywhere with it...I have been using Nodered now for close to a year, and never had problems like i am having now ☹

* * *

**TL;DR**

- Trouble starting a Nodered Docker Container via docker stack deploy
- Started _I Think_ since updating node-red-dashboard to version 2.19.4
- Now unable to start the nodered container _at all_ via docker deploy commands
- Have tried numerous ways to tackle the problem but it still persists

* * *

**Setup**  
(8x) Cluster of Raspberry Pi 4 -(Hostnames: p1, p2, p3...etc...p7, p8) all running Raspbian Buster Lite  
_[Since problems have started I am only deploying on a single node - p1 (docker manager)]_  
Running Docker v.19.03.8  
Node-red image: nodered/node-red:1.0.4-12-arm32v7  
Node-red-dashboard@2.19.4

Basically, this setup has been running fine for months (actually using dashboard v2.19.3) until I recently tried to update the dashboard node to v.2.19.4. Now my Nodered container will not start at all...

I am bind mounting the host directory /data/nodered/data to the container volume  
The directory \</data/nodered/data\> contains...

```auto
pi@p1:/data/nodered/data $ ls -aln
total 90
drwxr-xr-x 5 1000 1000 4096 Mar 30 23:56 .
drwxr-xr-x 9 1000 1000 4096 Mar 30 03:15 ..
-rw-r--r-- 1 0 0 15284 Mar 30 23:56 .config.json
-rw-r--r-- 1 0 0 15285 Mar 30 22:46 .config.json.backup
-rw-r--r-- 1 0 0 483 Mar 30 22:19 flows.json
drwxr-xr-x 3 0 0 4096 Mar 30 21:26 lib
drwxr-xr-x 70 1000 1000 4096 Mar 30 22:44 node_modules
-rw-r--r-- 1 0 0 232 Mar 30 22:44 package.json
-rw-r--r-- 1 1000 1000 26776 Mar 30 22:45 package-lock.json
-rw-r--r-- 1 0 0 12478 Mar 30 21:26 settings.js
drwxr-xr-x 2 1000 1000 4096 Mar 30 22:07 tmp

```

^ Sorry if the formatting messes up here, i will try and fix it if it does..

My compose.yml file for docker stack deploy.....contains;

```auto
services:
  nodered:
     image: nodered/node-red:1.0.3-4-12-arm32v7
# image: nodered/node-red:1.0.3-4-12-minimal-arm32v7
# image: nodered/node-red:1.0.4-12-arm32v7
# image: nodered/node-red:1.0.4-12-minimal-arm32v7
# entrypoint: "npm start -- --userDir /data --safe"
    ports:
      - "1880:1880"
    user: "0"
# user: "1000:1000"
    environment:
      TZ: "Europe/London"
    deploy:
      mode: replicated
      replicas: 1
      restart_policy:
         condition: any
         delay: 25s
         max_attempts: 5
         window: 90s
      placement:
         constraints:
            - node.hostname==p1
    volumes:
      - "/data/nodered/data/:/data/"
      - "/etc/timezone:/etc/timezone:ro"
      - "/etc/localtime:/etc/localtime:ro"

```

The logs i am getting via docker logs -f stack\_nodered are not very helpful.  
I ahve also set the log level to 'trace' but there's still not much to deliver there

```auto
pi@p1:~ $ docker service logs -f stack_nodered
stack_nodered.1.hrljun5ah6oh@p1 | 
stack_nodered.1.hrljun5ah6oh@p1 | > node-red-docker@1.0.3 start /usr/src/node-red
stack_nodered.1.hrljun5ah6oh@p1 | > node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"
stack_nodered.1.hrljun5ah6oh@p1 | 
stack_nodered.1.hrljun5ah6oh@p1 | 30 Mar 23:25:06 - [info] 
stack_nodered.1.hrljun5ah6oh@p1 | 
stack_nodered.1.hrljun5ah6oh@p1 | Welcome to Node-RED
stack_nodered.1.hrljun5ah6oh@p1 | ===================
stack_nodered.1.hrljun5ah6oh@p1 | 
stack_nodered.1.hrljun5ah6oh@p1 | 30 Mar 23:25:06 - [info] Node-RED version: v1.0.3
stack_nodered.1.hrljun5ah6oh@p1 | 30 Mar 23:25:06 - [info] Node.js version: v12.15.0
stack_nodered.1.hrljun5ah6oh@p1 | 30 Mar 23:25:06 - [info] Linux 4.19.97-v7l+ arm LE
stack_nodered.1.hrljun5ah6oh@p1 | 30 Mar 23:25:06 - [info] Loading palette nodes
stack_nodered.1.xcygutoh0ga2@p1 | 
stack_nodered.1.xcygutoh0ga2@p1 | > node-red-docker@1.0.3 start /usr/src/node-red
stack_nodered.1.xcygutoh0ga2@p1 | > node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"
stack_nodered.1.xcygutoh0ga2@p1 | 
stack_nodered.1.xcygutoh0ga2@p1 | 30 Mar 23:27:09 - [info] 
stack_nodered.1.xcygutoh0ga2@p1 | 
stack_nodered.1.xcygutoh0ga2@p1 | Welcome to Node-RED
stack_nodered.1.xcygutoh0ga2@p1 | ===================
stack_nodered.1.xcygutoh0ga2@p1 | 
stack_nodered.1.xcygutoh0ga2@p1 | 30 Mar 23:27:09 - [info] Node-RED version: v1.0.3
stack_nodered.1.xcygutoh0ga2@p1 | 30 Mar 23:27:09 - [info] Node.js version: v12.15.0
stack_nodered.1.xcygutoh0ga2@p1 | 30 Mar 23:27:09 - [info] Linux 4.19.97-v7l+ arm LE
stack_nodered.1.xcygutoh0ga2@p1 | 30 Mar 23:27:10 - [info] Loading palette nodes

```

_I know the logs show the image for **version 1.0.3** - but it's exactly the same for v.1.0.4_  
The log just repeats and repeats without much useful information.

If i change the settings.js so include trace debugging, then the log shows the palette nodes being loaded - it reaches up to 'node-red-tail' before it bums out and restarts. But i know that node package comes pre-installed with node-red, so that cant be the problem.

**Things I have Tried**

1. I have tried to use the --safe flag to start without the flows running  
In docker compose...

```auto
  entrypoint: "npm start -- --userDir /data --safe"

```

```
  -- This also doesnt start - telling me my flow.json file is probably OK

```

1. I have tried using several images - 1.0.4....1.0.3....1.0.4-minimal......1.0.3-minimal  
-- Same thing happens - so it cant be the image version

2. I have tried $ 'docker exec -it \<\> /bin/bash' into the container so I can npm install node-red-dashboard@2.19.3 manually,  
-- When the container is restarted it crashes and never starts.

3. I removed node-red-dashboard from node\_modules and from package-lock.json  
-- Still crashes

4. More drastically, i have tried to remove everything from the /data folder and redeployed the container.  
-- The container then starts, but as soon as i re-download dashboard from the palette manager (it downloads v.2.19.4) then the container is unable to start when stopped via docker.

5. I have tried using;

```auto
docker run -it --name nodered -p 1880:1880 nodered/node-red:1.0.4-12-arm32v7

```

```
  -- This works - but obviously doesnt use my filesystem on the host, which leads me to believe theres a problem with one of the files in the /data/nodered/data folder (maybe corruption). But i have cleaned out that folder, started from a fresh nodered container and downloaded dashboard - then it doesnt restart.

```

So, as you can tell I cannot get to the bottom of this problem, when i try to install node-red-dashboard@2.19.3 manually (I only have a short window to do this before the container is self-destructed and i get thrown out of the bash session)

```auto
pi@p1:~ $ docker exec -it <container> /bin/bas
bash-5.0# npm install node-red-dashboard@2.19.3

```

It comes back with:

```auto
bash-5.0# npm install --reinstall node-red-dashboard@2.19.3
npm notice created a lockfile as package-lock.json. You should commit this file.
+ node-red-dashboard@2.19.3
added 47 packages from 42 contributors and audited 1527 packages in 21.641s

13 packages are looking for funding
  run `npm fund` for details

found 9 low severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details
bash-5.0# 

```

But then when i stop the container and restart i get the same thing and it doesn't start up.

* * *

Are there any other ways to debug the Nodered startup??  
I am now losing the plot and cannot get my head from unintentionally banging itself on the desk...

- I don't think its a networking issue - as the container will run in standalone mode (docker run..)
- I don't think its a flows.json problem - as when removed the problem still persists
- I don't think its a docker image problem - as the same problem exhibits over several different images
- I think this could be down to either;
- New dashboard package incompatible with Nodered v1.0.4 _or_ docker
- Something is corrupt inside my node\_modules folder or package-lock.json file (cant upload as new user) - but starting with a fresh version of each of these doesnt help...

Any help is much appreciated, and if any more info is needed - let me know an ill post back

Thanks!

---

<div class="post-metadata">

**Author:** ![Mozz164](https://avatars.discourse-cdn.com/v4/letter/m/ecc23a/32.png) [@Mozz164](https://discourse.nodered.org/u/Mozz164)\
**Post date:** [31 March 2020 15:52 UTC](https://discourse.nodered.org/t/trouble-with-docker-nodered-1-0-4-dashboard-2-19-4/23930/2 "2020-03-31T15:52:08Z")

</div>

Problem definitely seems to be with the node\_modules folder

If i comment out -"/data/nodered/data/:/data/"  
from the docker-compose.yml file, then it will run...so i did a little more digging

changing flows.json to .flows.json -\> container still doesnt start  
changing package-lock.json to .package-lock.json -\> still doesnt start  
changing node\_modules to .node\_modules -\> container starts

How do i find a problem with the node\_modules folder???  
i have tried deleting it entirely, the container starts but then i download dashboard through the palette and then it doesnt start again....help..!!! ☹

...Will keep digging...

---

<div class="post-metadata">

**Author:** ![janvda](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/janvda/32/234_2.png) [@janvda](https://discourse.nodered.org/u/janvda)\
**Post date:** [2 April 2020 06:45 UTC](https://discourse.nodered.org/t/trouble-with-docker-nodered-1-0-4-dashboard-2-19-4/23930/3 "2020-04-02T06:45:51Z")

</div>

Have you tried older version of docker image ?

I am currently using `nodered/node-red:1.0.3-2-12` on my intel NUC without an issue.

---

<div class="post-metadata">

**Author:** ![janvda](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/janvda/32/234_2.png) [@janvda](https://discourse.nodered.org/u/janvda)\
**Post date:** [2 April 2020 07:09 UTC](https://discourse.nodered.org/t/trouble-with-docker-nodered-1-0-4-dashboard-2-19-4/23930/4 "2020-04-02T07:09:57Z")

</div>

Justed tested your versions of nodered and dashboard on my intel NUC and that is working for me.

```auto
Copying settings.js to /data folder
Starting node-red ...
> node-red-docker@1.0.4 start /usr/src/node-red
> node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"
2 Apr 08:58:22 - [info] 
Welcome to Node-RED
===================
2 Apr 08:58:22 - [info] Node-RED version: v1.0.4
2 Apr 08:58:22 - [info] Node.js version: v12.16.1
2 Apr 08:58:22 - [info] Linux 4.18.0-147.3.1.el8_1.x86_64 x64 LE
2 Apr 08:58:22 - [info] Loading palette nodes
2 Apr 08:58:24 - [info] Dashboard version 2.19.4 started at /ui
2 Apr 08:58:24 - [info] Settings file : /data/settings.js
2 Apr 08:58:24 - [info] Context store : 'default' [module=memory]
2 Apr 08:58:24 - [info] User directory : /data
2 Apr 08:58:24 - [info] Server now running at http://127.0.0.1:1880/
2 Apr 08:58:24 - [info] Active project : node-red-corona-comparison-hubei
2 Apr 08:58:24 - [info] Flows file : /data/projects/node-red-corona-comparison-hubei/flow.json
2 Apr 08:58:24 - [info] Starting flows
2 Apr 08:58:24 - [info] Started flows
2 Apr 09:03:32 - [info] Stopping flows
2 Apr 09:03:32 - [info] Stopped flows
2 Apr 09:03:32 - [info] Starting flows
2 Apr 09:03:33 - [info] Started flows

```

---

<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:** [2 May 2020 07:10 UTC](https://discourse.nodered.org/t/trouble-with-docker-nodered-1-0-4-dashboard-2-19-4/23930/5 "2020-05-02T07:10:02Z")

</div>

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