Container attachment gets interrupted. about node-red-docker HOT 4 CLOSED

UPDATE:

Container is indeed crashing, but it's restarting automatically afterwards which is what made me reach the previous conclusion (somebody else had changed its behaviour and I wasn't informed).

Some extra information: System is Ubuntu 16.04.

Docker version:

Client:
Version: 17.03.1-ce
API version: 1.27
Go version: go1.7.5
Git commit: c6d412e
Built: Mon Mar 27 17:14:09 2017
OS/Arch: linux/amd64

Server:
Version: 17.03.1-ce
API version: 1.27 (minimum version 1.12)
Go version: go1.7.5
Git commit: c6d412e
Built: Mon Mar 27 17:14:09 2017
OS/Arch: linux/amd64
Experimental: false

Docker info

Containers: 13
Running: 13
Paused: 0
Stopped: 0
Images: 29
Server Version: 17.03.1-ce
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 192
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 4ab9917febca54791c5f071a9d1f404867857fcc
runc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe
init version: 949e6fa
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.4.0-81-generic
Operating System: Ubuntu 16.04.2 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 5.82 GiB
Name: fvalleubuntu
ID: MMO6:376F:EERK:VM55:WW53:KSF6:DQFB:2QIH:APEB:RX6Z:X5IK:4U4F
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

from node-red-docker.

Hello @Wcctnoam, what nodes are you using? is this with a blank instance or do you have lots of custom flows?

Looking at the error message, it's an internal core-dump in the node.js runtime. If you run Node-RED locally with the same configuration, do you see the same error?

from node-red-docker.

Hello again. I feel really silly, but I've isolated the problem enough to know the cause comes from one of our flows, which I cannot share. I will say I highly suspect the nodes from the postgrestor repository, in case somebody else comes across a similar problem, and that stopping and restarting Docker itself helped quite a bit, although I suspect it only kicked the can down the road.

This issue is as good as closed for me now, since no more help can be provided for me. Thank you for the reply anyway.

from node-red-docker.

This is the kind of issue I like, one that fixes itself ;)

from node-red-docker.