Hi all,

 

I am having some weird issues which looks like its coming from my Docker Engine.

 

The issue started about a week ago and comes across as these symptoms

1. Dockers seem unresponsive i.e. Emby Tvheadend etc..

2. When I go to the Docker menu  - They are all showing as running however when I try to goto their respective Webui they are not responsive

3. I Dont think stopping and Starting makes any difference

 

Below are a set of steps I have tried

1. Delete Docker Img - re-create and add all containers back

2. Docker image is 30GB with 5GB being used

3. stopping and starting docker engine from command line via  /etc/rc.d/rc.docker stop / start seems to restore things

 

I have ran a diagnostic and I see these two errors come up int the Docker log file

 

time="2018-08-02T06:17:24.90385105+10:00" level=info msg="stopping containerd after receiving terminated" 
time="2018-08-03T17:51:27.298044846+10:00" level=info msg="stopping containerd after receiving terminated" 
 

Any advice or thoughts to help troubleshoot would be ace!

 

Are you really running the old version of unRAID mentioned in the subject line?

Yes, should I upgrade? LOL

 

if so I will have to reschedule the upgrade in with my wife!

 

Is it pretty easy to upgrade now? I know there was quite a lot of manual steps when 6.4 6.5

Ok I have tried to see if there is a specific container causing this issue but cant seem to find it.

 

The weird thing is that CA Advisor shows memory at 96% however when i run 

Docker stats

The memory on each container is hardly being used.

 

Any thoughts anyone? or what else to check for?

 

 

Since you're not in a specific container, cAdvisor is showing the total memory used on your system, including some caching.  Getting the stats on a particular container will show the memory usage of it, exluding caching.

 

Diagnostics (after doing whatever you do to get the symptoms in the OP) is always a plus when posting

Edited August 5, 20187 yr by Squid

Ok Just a heads up on this

 

I pretty sure it was my Unifi container causing issues after an update.

 

I did however upgrade to 6.5.3 and everything works fine. I still need to try to diagnose the issues with the Unifi container