Docker Service failed to start.

[VIDEOMED]

Dear
please help
Until today, all Dockers were working normally
Suddenly I got a message.
What do you have to do?
I am not fluent in UNRAID

DockerClient.php

[Squid]

You need to post your diagnostics not the php code

[VIDEOMED]

1 hour ago, Squid said:

You need to post your diagnostics not the php code

 

ErrorWarningSystemArrayLogin.txt

[Squid]

Please post the diagnostics 

[VIDEOMED]

1 hour ago, Squid said:

Please post the diagnostics 

ErrorWarningSystemArrayLogin

Dec 10 12:16:05 SOFIA root: Fix Common Problems: Warning: unRaids built in FTP server is currently disabled, but users are defined
Dec 10 12:16:37 SOFIA root: Total Spundown: 0
Dec 10 12:17:22 SOFIA emhttpd: cmd: /usr/local/emhttp/plugins/ProFTPd/scripts/rc.ProFTPd removeplg
Dec 10 12:17:23 SOFIA sudo: root : PWD=/ ; USER=root ; COMMAND=/etc/rc.d/rc.inetd restart
Dec 10 12:17:24 SOFIA root: plugin: creating: /tmp/ProFTPd-script - from INLINE content
Dec 10 12:17:24 SOFIA root: plugin: running: /tmp/ProFTPd-script
Dec 10 12:18:12 SOFIA flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup.php update
Dec 10 12:20:04 SOFIA sSMTP[31533]: Creating SSL connection to host
Dec 10 12:20:05 SOFIA sSMTP[31533]: SSL connection using TLS_AES_256_GCM_SHA384
Dec 10 12:20:13 SOFIA flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup.php update
Dec 10 12:20:13 SOFIA sSMTP[31533]: Sent mail for [email protected] (221 2.0.0 Bye) uid=0 username=root outbytes=854
Dec 10 12:21:15 SOFIA flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup.php update
Dec 10 12:21:37 SOFIA root: Total Spundown: 0
Dec 10 12:26:37 SOFIA root: Total Spundown: 0
Dec 10 12:31:37 SOFIA root: Total Spundown: 0
Dec 10 12:34:36 SOFIA emhttpd: spinning down /dev/sdb
Dec 10 12:34:36 SOFIA emhttpd: spinning down /dev/sdc
Dec 10 12:36:14 SOFIA emhttpd: spinning down /dev/sdd
Dec 10 12:36:37 SOFIA root: Total Spundown: 2
Dec 10 12:41:37 SOFIA root: Total Spundown: 2
Dec 10 12:46:37 SOFIA root: Total Spundown: 2
Dec 10 12:51:37 SOFIA root: Total Spundown: 2
Dec 10 12:56:37 SOFIA root: Total Spundown: 2
Dec 10 13:01:37 SOFIA root: Total Spundown: 2
Dec 10 13:06:37 SOFIA root: Total Spundown: 2
Dec 10 13:07:46 SOFIA emhttpd: read SMART /dev/sdd
Dec 10 13:07:46 SOFIA emhttpd: read SMART /dev/sdb
Dec 10 13:07:46 SOFIA emhttpd: read SMART /dev/sdc
Dec 10 13:11:37 SOFIA root: Total Spundown: 0
Dec 10 13:16:37 SOFIA root: Total Spundown: 0
Dec 10 13:21:37 SOFIA root: Total Spundown: 0
Dec 10 13:26:37 SOFIA root: Total Spundown: 0
Dec 10 13:31:37 SOFIA root: Total Spundown: 0
Dec 10 13:33:02 SOFIA webGUI: Successful login user root from 192.168.1.146
Dec 10 13:34:06 SOFIA flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup.php update
Dec 10 13:35:06 SOFIA flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup.php update
Dec 10 13:36:38 SOFIA root: Total Spundown: 0
Dec 10 13:41:38 SOFIA root: Total Spundown: 0
Dec 10 13:46:38 SOFIA root: Total Spundown: 0

[Squid]

That is not the diagnostics  Post the entire zip file.  Look at the link

[VIDEOMED]

i try syslog server but no .zip file appears
I'm leaving in a moment. I'll be back on Monday

[trurl]

https://wiki.unraid.net/Manual/Troubleshooting#System_Diagnostics

 

[VIDEOMED]

The file diagnostic

sofia-diagnostics-20211210-1203.zip

[VIDEOMED]

The file diagnostic new

sofia-diagnostics-20211213-1042.zip

[trurl]

docker.img corrupt. Probably because you have been filling it.

 

You have it set to 55G, which is another reason I suspect you have been filling it. 20G is usually much more than enough, and making it larger won't fix whatever is filling it, it will only make it take longer to fill. I run 15-20 dockers and they use about half of 20G I have allocated.

 

The usual cause of filling docker.img is an application writing to a path that doesn't correspond to a container path in the mappings, case-sensitive.

 

You will have to delete and recreate docker.img, I recommend 20G

 

https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file

 

Then reinstall your dockers.

 

https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications

 

Probably best to take them one at a time and look at all the paths specified within each application.

[trurl]

Also your system share has files on the array, might as well clean that up too since you are recreating docker.img

 

Do you have any VMs?

[VIDEOMED]

yes I have 5 VMs

[trurl]

What do you get from the command line with this?

ls -lah /mnt/disk1/system

and this?

ls -lah /mnt/cache/system

[VIDEOMED]

root@SOFIA:~# ls -lah /mnt/disk1/system
total 4.0K
drwxrwxrwx  4 nobody users   47 Apr 16  2021 ./
drwxrwxrwx 18 nobody users 4.0K Dec 13 18:12 ../
drwxrwxrwx  2 nobody users   24 Apr 16  2021 docker/
drwxrwxrwx  2 nobody users   33 Apr 16  2021 libvirt/
root@SOFIA:~# ls -lah /mnt/cache/system
total 16K
drwxrwxrwx 1 nobody users 26 Apr 16  2021 ./
drwxrwxrwx 1 nobody users 42 Dec 13 18:12 ../
drwxrwxrwx 1 nobody users  0 Dec 14 07:48 docker/
drwxrwxrwx 1 nobody users  0 Apr 16  2021 libvirt/
root@SOFIA:~#

[VIDEOMED]

Thank you
After removing docker.img, the system rebuilt very quickly
I changed the size to 20GB.
Previously, I increased the size from 20GB to 50GB as there was a signal that there was not enough space.
When I first installed UNRAID, I tested various Dockers. Old Dockers probably remained. After rebuilding, docker.img is much smaller

[trurl]

5 hours ago, VIDEOMED said:

docker.img is much smaller

If it seems to grow even if you don't install new dockers then you need to look at your applications to make sure they aren't writing to an unmapped path.

 

Post new diagnostics if you want us to take another look.

[VIDEOMED]

I have multiple dockers installed. I want to test them docker.image has a limit of 20GB. But the usage is 82%

sofia-diagnostics-20211214-1532.zip

[trurl]

6 minutes ago, VIDEOMED said:

I have multiple dockers installed. I want to test them docker.image has a limit of 20GB. But the usage is 82%

I usually run 15-20 dockers and my usage is barely half of the 20G I have allocated.

 

Those diagnostics show docker.img is still allocated 55G, but as you say, it is 82% full.

 

You have to delete and recreate docker.img to get it reduced to the 20G you have set then reinstall your dockers. See the wiki links I posted earlier.

[GreenEyedMonster]

How can you track down what is filling up the docker.img??  Mine suddenly exploded for no reason.

[VIDEOMED]

Thank you for your help
All Dockers are working fine.
I have a question
Why can't the docker.img file be large?
Maybe you need to create several smaller ones.

[trurl]

Just now, VIDEOMED said:

Why can't the docker.img file be large?

It doesn't need to be and if it grows that indicates configuration problems.

 

[trurl]

12 hours ago, GreenEyedMonster said:

track down what is filling up the docker.img

 

On 12/13/2021 at 9:32 AM, trurl said:

The usual cause of filling docker.img is an application writing to a path that doesn't correspond to a container path in the mappings, case-sensitive.

Click the Container Size button on the Docker page and post a screenshot.

 

I may split your post and any replies to another thread since this one belongs to OP

[VIDEOMED]

[trurl]

That looks fine