Hello, 

 

I seem to be having an issue with my system. 

I've been having some problems and weird behaviour with some of my docker container but now I need some help. 

 

It seems like at the moment the log is compleatly filled up, only a little after 24 hours after restarting the system. 

I don't want to restart the system right away because I want to find out what is causing the fill up, if I have some misconfigured container or something like that. 

 

Also, I have an error on my docker page: 

Quote

failed to open stream: Read-only file system in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 90

I tried looking for answers about this and one thread talked about ata errors causing the docker file to be corrupted. 

I had that issue two weeks ago so I was wondering if I had to rebuild my docker file or if the issue is related to the log issue. 

 

I have attached the diagnostic file here so hopefully that helps finding the issue.

 

Here is the post with the ata errors and the diagnostic files 

 

Thanks.

 

heimanas-diagnostics-20220812-1126.zip

Docker image is corrupt, apparently because it ran out of space, delete and re-create.

1 hour ago, JorgeB said:

Docker image is corrupt, apparently because it ran out of space, delete and re-create.

Hey JorgeB, 

Yes, that seems to be because the Log partition is full. 

 

And it seems to be that the docker logs are filling up the partition:

Quote

root@Heimanas:~# du -sm /var/log/*
0       /var/log/btmp
0       /var/log/cron
0       /var/log/debug
1       /var/log/dmesg
128     /var/log/docker.log
0       /var/log/faillog
0       /var/log/lastlog
0       /var/log/libvirt
0       /var/log/maillog
0       /var/log/messages
0       /var/log/nfsd
0       /var/log/nginx
0       /var/log/packages
0       /var/log/pkgtools
0       /var/log/plugins
0       /var/log/pwfail
0       /var/log/removed_packages
0       /var/log/removed_scripts
1       /var/log/samba
0       /var/log/scripts
0       /var/log/secure
0       /var/log/setup
0       /var/log/spooler
0       /var/log/swtpm
1       /var/log/syslog
0       /var/log/vfio-pci
1       /var/log/wtmp

 

Any way I can find out why?

1 hour ago, kjarri said:

seems to be because the Log partition is full. 

 

You have that exactly backwards.

 

Filling logs cannot corrupt docker.img. These are in totally separate spaces. Logs are in RAM for one thing. You filled docker.img and corrupted it, and the corrupt docker.img has caused a lot of log entries, filling the log space.

 

The usual reason for filling docker.img is an application writing to a path that isn't mapped.

 

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