# Docker / Node-RED healthcheck.js

**URL:** <https://www.wago.community/t/docker-node-red-healthcheck-js/722>\
**Category:** Hardware and Linux\
**Tags:** docker, linux\
**Created:** [December 20, 2023, 10:28pm UTC](https://www.wago.community/t/docker-node-red-healthcheck-js/722 "2023-12-20T22:28:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![MikePsaltis](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/mikepsaltis/32/47_2.png) [@MikePsaltis](https://www.wago.community/u/MikePsaltis)\
**Post date:** [December 20, 2023, 10:28pm UTC](https://www.wago.community/t/docker-node-red-healthcheck-js/722/1 "2023-12-20T22:28:08Z")

</div>

Hello,

I am running a Node-RED container in parallel to a CODESYS application on a PFC200 controller.

I am looking for some information on healthcheck.js and seeing with htop that a healthcheck.js process runs about every minute. This is causing the CPU to increase by 45% (and max at 100%). The CODESYS webvisu freezes when the healtcheck.js process is run.

Is this specific to Docker?  
Is it acceptable to use --no-healthcheck to disable this? I ran my container with this flag an no longer see this process.

Here is more information:

Thanks!

healthcheck.js file location:

 ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/1X/de2e2b1ae8096d271b9da864625cca619d1441d3.png)  
 ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/1X/223692db477b1dd618ce46ebcdc2fa90f6166fcd.png)

---

<div class="post-metadata">

**Author:** ![WagoIcard](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagoicard/32/1508_2.png) [@WagoIcard](https://www.wago.community/u/WagoIcard)\
**Post date:** [January 5, 2024, 4:18am UTC](https://www.wago.community/t/docker-node-red-healthcheck-js/722/2 "2024-01-05T04:18:57Z")

</div>

Hello,  
Is this the default node-red docker ? or a modified one ?  
Does the freeze if for around 4s ? in that case it could be waiting for the timeout and blocking everything else.  
you could uncomment the console.log lines and see in the console of the docker what happened.

---

<div class="post-metadata">

**Author:** ![Boettcher](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/boettcher/32/1822_2.png) [@Boettcher](https://www.wago.community/u/Boettcher)\
**Post date:** [April 15, 2026, 7:06pm UTC](https://www.wago.community/t/docker-node-red-healthcheck-js/722/3 "2026-04-15T19:06:08Z")

</div>

I am currently having this same issue with the default Docker image and a CC100.

---

<div class="post-metadata">

**Author:** ![WagoIcard](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagoicard/32/1508_2.png) [@WagoIcard](https://www.wago.community/u/WagoIcard)\
**Post date:** [April 20, 2026, 12:26am UTC](https://www.wago.community/t/docker-node-red-healthcheck-js/722/4 "2026-04-20T00:26:04Z")

</div>

This is interesting, Maybe we could try to see if there is a posibility to have this task be running on the background in a non blocking process ?

Also for your question @MikePsaltis yes you can disable it but the container won’t automatically restart on nodered-crash.

Also maybe checking for the nodered PID in the process would be a better solution no instead of using the web page ?