Docker using 51%

[JGKahuna]

I have one Docker running DUCKDNS, and even when I stop it, I still get 51% of the Ram being used? If I start another docker I get a warning message. I have even Pinned the cpu on the Duck DNS to only use a few cores.

Edited April 14, 2023 by JGKahuna
spelling

[Vr2Io]

11 minutes ago, JGKahuna said:

I still get 51% of the Ram being used?

This is docker image file usage.

[JGKahuna]

19 minutes ago, JGKahuna said:

Actually I get a warning that it is running out of space now. It ran up to 100% usage. And would not pull down another docker image

Fixed, had to increase the disk size. 

[Vr2Io]

If need, you could recreate (cleanup) the image in different way.

 

 

Edited April 14, 2023 by Vr2Io

[itimpi]

5 hours ago, JGKahuna said:

Actually I get a warning that it is running out of space now. It ran up to 100% usage.

This typically means that at least one of your docker containers is writing internally to the docker image file when ideally the location it is using should be mapped to external storage on the Unraid host.   You really want the docker image file to only contain static binaries if at all possible.

[JGKahuna]

OK I found where to add up more space. It only had 20gigs of space.

 

[Hoopster]

13 minutes ago, JGKahuna said:

It only had 20gigs of space.

It is very uncommon to need a Docker image file larger than 20GB.  I have 15 active containers with only 54% usage in the docker.img.

 

If you get over 50% usage with just one or two Docker containers on a 20GB docker.img file, it is likely you have the problem mentioned above by @itimpi, a mis-configured container that is writing into docker.img.  If this is the case, increasing the size of the docker image file is a temporary fix and does not solve the problem.

Edited April 14, 2023 by Hoopster