# Docker container exits immediately

**URL:** <https://www.wago.community/t/docker-container-exits-immediately/163>\
**Category:** Node-RED\
**Tags:** pfc200, docker, codesys\
**Created:** [July 15, 2022, 8:56pm UTC](https://www.wago.community/t/docker-container-exits-immediately/163 "2022-07-15T20:56:37Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![RBSI](https://avatars.discourse-cdn.com/v4/letter/r/c57346/32.png) [@RBSI](https://www.wago.community/u/RBSI)\
**Post date:** [July 15, 2022, 8:56pm UTC](https://www.wago.community/t/docker-container-exits-immediately/163/1 "2022-07-15T20:56:37Z")

</div>

Hello Everyone,

i am trying to run node-red on my wago pfc200-8204 which is assigned by a DHCP server. i am trying to run command to start node-red however it creates the container to start it, for momentarily and then exits immediately. Is this can happen due to firmware as i just changed firmware recently for factory resetting. Here is more detail about my error.

 ![Container just exits](https://us1.discourse-cdn.com/flex016/uploads/wago/original/1X/76c010aae499f9e05bd42d4ab22066dcfe44728f.png)

root@PFC200-41E863:~ docker start 30bffb3b7ff0  
30bffb3b7ff0  
root@PFC200-41E863:~ docker ps  
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES  
30bffb3b7ff0 nodered/node-red “npm --no-update-not…” 3 minutes ago Up 2 seconds (health: starting) 0.0.0.0:1880-\>1880/tcp wago-node-red  
root@PFC200-41E863:~ docker ps -a  
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES  
30bffb3b7ff0 nodered/node-red “npm --no-update-not…” 3 minutes ago Exited (135) 6 seconds ago wago-node-red  
root@PFC200-41E863:~ timed out waiting for input: auto-logout  
Connection to 192.168.1.20 closed.

Please help. Thank you

---

<div class="post-metadata">

**Author:** ![quenorha](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/quenorha/32/429_2.png) [@quenorha](https://www.wago.community/u/quenorha)\
**Post date:** [July 18, 2022, 6:02am UTC](https://www.wago.community/t/docker-container-exits-immediately/163/2 "2022-07-18T06:02:10Z")

</div>

Hello,  
Take a look to the logs to see what’s wrong with this container :

```auto
docker logs wago-node-red

```

Or start the container interactively (-ti instead of -d)

---

<div class="post-metadata">

**Author:** ![RBSI](https://avatars.discourse-cdn.com/v4/letter/r/c57346/32.png) [@RBSI](https://www.wago.community/u/RBSI)\
**Post date:** [July 18, 2022, 4:49pm UTC](https://www.wago.community/t/docker-container-exits-immediately/163/3 "2022-07-18T16:49:42Z")

</div>

Hello thanks for the help. i actually think that if you install older firmware on wago (3.0.59 (12) I believe), we cannot run latest versions of the node-red somehow. i installed version 8 of the node-red, which is quite old and it ran alright on the web browser.

Thanks

---

<div class="post-metadata">

**Author:** ![RBSI](https://avatars.discourse-cdn.com/v4/letter/r/c57346/32.png) [@RBSI](https://www.wago.community/u/RBSI)\
**Post date:** [July 18, 2022, 7:26pm UTC](https://www.wago.community/t/docker-container-exits-immediately/163/4 "2022-07-18T19:26:12Z")

</div>

![Error](https://us1.discourse-cdn.com/flex016/uploads/wago/original/1X/8ca8f43b0faa5c98f831d3ad35a7f33dffbfe3de.png)

This is the error i am facing if i try to run newer image of the node-red instead of rpi-v8 version image.  
Not sure how to avoid this or what is causing it.

---

<div class="post-metadata">

**Author:** ![WagoKurt](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagokurt/32/11_2.png) [@WagoKurt](https://www.wago.community/u/WagoKurt)\
**Post date:** [July 26, 2022, 4:33pm UTC](https://www.wago.community/t/docker-container-exits-immediately/163/5 "2022-07-26T16:33:13Z")

</div>

The 750-8202 has less memory than the newer 750-8212. Because of this, starting with FW19 requires a different firmware. These can be downloaded & installed with e!COCKPIT directly if the PFC is FW12 or higher (see image below). If your PFC is running FW8, you will need to update with an SD card. Here is FW17 link, which you can unzip and image.

[https://github.com/WAGO/pfc-firmware/releases/download/17-v03.05.10/WAGO\_FW0750-8xxx\_V030510\_IX17\_r50384.7z](https://github.com/WAGO/pfc-firmware/releases/download/17-v03.05.10/WAGO_FW0750-8xxx_V030510_IX17_r50384.7z)

Once this is installed you can update using e!COCKPIT and select the version for the Generation 1 PFC200.  
I would recommend FW19+ if using Docker.

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

---

<div class="post-metadata">

**Author:** ![RBSI](https://avatars.discourse-cdn.com/v4/letter/r/c57346/32.png) [@RBSI](https://www.wago.community/u/RBSI)\
**Post date:** [July 27, 2022, 9:16pm UTC](https://www.wago.community/t/docker-container-exits-immediately/163/6 "2022-07-27T21:16:00Z")

</div>

Hello thank you very much for the response. the source of the problem was :

version 3.0.0 of the Node-RED Docker container will not run on old versions of Docker that do not support 64bit time on a 32bit OS.

from this resource.

> <https://stackoverflow.com/questions/73028520/why-does-the-docker-container-exits-immediately-on-plc>

---

<div class="post-metadata">

**Author:** ![wagojesse](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagojesse/32/8_2.png) [@wagojesse](https://www.wago.community/u/wagojesse)\
**Post date:** [July 28, 2022, 10:38pm UTC](https://www.wago.community/t/docker-container-exits-immediately/163/7 "2022-07-28T22:38:52Z")

</div>

Version 3.0 works well on Generation 2 PFC controllers. The 8204 is a generation 1 and was replaced with a higher performing, expanded storage version with no price increase a few years ago for this reason. The 750-8214 runs NR version 3.0 very nicely. I would suggest upgrading the controller to allow for this functionality.

---

<div class="post-metadata">

**Author:** ![Manik](https://avatars.discourse-cdn.com/v4/letter/m/c37758/32.png) [@Manik](https://www.wago.community/u/Manik)\
**Post date:** [July 29, 2022, 7:39am UTC](https://www.wago.community/t/docker-container-exits-immediately/163/8 "2022-07-29T07:39:47Z")

</div>

I got the same issue. Try adding  
–security-opt=seccomp=unconfined`to the`docker run` command

it worked for me
