You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Storage space on my dedicated server was slowly diminishing. After some research I pinpointed the culprit to the Kaizoku container. After recreating the container 147GB was freed up.
Before container recreation:
After container recreation:
My assumption is that the downloaded chapters are stored within the kaizoku container and never cleaned up. I do have binded volumes for the logs, so unless they are also created within the container and just copied to /logs for some reason, I doubt the logs are to blame.
Reproduction steps
Create Kaizoku containers using :latest
Run docker system df and take note of the Containers size
Download a manga with many chapters within Kaizoku
Wait until finished and run docker system df again and compare the Contains sizes
Do this for a week and see the continual growth.
Expected behavior
Container size should not grow continually.
Additional context
Was running :latest but likely v1.2.1 or 1.3.0 (unfortunately I am unsure here as I recreated the container)
The text was updated successfully, but these errors were encountered:
Describe the bug
Storage space on my dedicated server was slowly diminishing. After some research I pinpointed the culprit to the Kaizoku container. After recreating the container 147GB was freed up.
Before container recreation:
After container recreation:
My assumption is that the downloaded chapters are stored within the kaizoku container and never cleaned up. I do have binded volumes for the logs, so unless they are also created within the container and just copied to /logs for some reason, I doubt the logs are to blame.
Reproduction steps
docker system df
and take note of the Containers sizedocker system df
again and compare the Contains sizesExpected behavior
Container size should not grow continually.
Additional context
Was running :latest but likely v1.2.1 or 1.3.0 (unfortunately I am unsure here as I recreated the container)
The text was updated successfully, but these errors were encountered: