Node-red container in docker: How do I get out of a Restart Loop?

General
1

I was configuring my node-red container to my mininet container both under the same docker, and when I went to change setting.json properties I believe I might have doubled a line that caused a syntax error to occur. Ever since, I have been getting this error below.

image
image882×259 18.9 KB

Whenever I try access node-red is keeps giving me this error saying that it is restarting. In this image below I tried entering in safe mode.

image

I am currently using double RDP to access this and I am working in Rocky Linux 8.10 for this. I am fairly new to node-red and I'm not familiar with recreating node-red. If I were to go the route of recreating are there parameters that need to be determined for node-red, or is it a simple installation. The sandbox I am working on is from a course, so I was not the one the initially installed this container. Is there anything I can do to solve this without having to recreate the container? It also seems to that the current node-red container is not on port 80 at the moment, so would I be able to create another one and connect it to the port without having to uninstall the current node-red container?

2

Here is the image the status of the containers.

image

3

Are you using the restart option in a docker compose file?

Or using the --restart option?

There is also systemctl which can potentially be restarting a failing docker image.

4

You can try injecting the "NODE_RED_ENABLE_SAFE_MODE=true" environment variable into the container to have it start but not run the flows, to give you the option to remove a broken node.