Jindo Posted April 14, 2023 Share Posted April 14, 2023 What does this mean and what can I do about it? I recently installed MongoDB, Elasticsearch, Graylog and Splunk and started receiving this notification. Thanks. Quote Link to comment
Hoopster Posted April 14, 2023 Share Posted April 14, 2023 22 minutes ago, Jindo said: What does this mean and what can I do about it? It likely means that one or more docker containers are mis-configured and are writing data into the docker.img file rather than another storage location. The default 20GB size for docker.img is usually more than enough for many containers. For example, I have 15 active docker containers and am using only 54% of docker.img. Start by clicking on the Container Size button in the docker tab to see if one or more containers appear to be particularly large in size. If so, verify the settings for the container to make sure something is not mis-configured. If in doubt about something post your configuration in the support thread for the docker container so others who use that container can help you. Quote Link to comment
Jindo Posted April 14, 2023 Author Share Posted April 14, 2023 Thanks Hoopster. These are my container sizes. The one that stood out is binhex-krusader at 2.38 GB. As you suggested, I posted something in the binex-krusader docker support thread. Quote Link to comment
Hoopster Posted April 14, 2023 Share Posted April 14, 2023 1 hour ago, Jindo said: The one that stood out is binhex-krusader at 2.38 GB I also have Binhex-Krusader and this is the normal container size for that container. A total size of 6.59 GB should not be 83% if you used the default image size of 20GB. Have you noticed the Docker utilization fluctuation up and down or is it always high? Quote Link to comment
Jindo Posted April 15, 2023 Author Share Posted April 15, 2023 Thanks Hoopster! Disk utilization stays high. The docker.img file size is 20 GB so like you said, the 83% doesn't make sense. Reading elseware on the Forum, I see that you've been helping others with this problem. I followed your suggestion to delete the docker.img file and have docker recreate it and the utilization dropped down to 34% I haven't determined which docker is filling up the docker.img file yet, but will start reviewing the templates. Thanks for your help with this. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.