Joly0
-
Posts
167 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by Joly0
-
-
1 minute ago, trurl said:
Often the cause of docker image corruption is overfilling it. And filling docker.img is often caused by an application writing to a path that isn't mapped.
I have been using default 20G docker.img for years with no problem, but I have never ran more than 16 containers.
Because it worked for you, doesnt mean it works for others aswell. But my issues with the image was not related to filling the docker.img. But even without those issues, switching to image might solve my issue for now, but doesnt solve the root cause of this issue here. So your comment is basically useless for me
-
41 minutes ago, Kilrah said:
Folder on a ZFS drive is known to cause these issues. Best to go back to image if you have a ZFS cache.
Also i know, that folder on a zfs drive is a known issue, but i havent found any bug report for this issue yet and i havent found a solution for it, and as people are starting or will start to use folder on zfs more and more, these issues will arrise more often aswell, without a proper solution other then "use image instead of folder", which btw is not official and not mentioned anywhere
-
I know, that an image will probably solve the issue for me, but as i said, it wont solve the root cause. Also i had far worse issues with an image compared to the folder. So i will 100% not switch back to an image.
-
tower-diagnostics-20231129-0102.zipOk, here is the diagnostics. Btw, i updated to 6.12.5 stable and both bugs still appear
-
Just wanted to add, that my download speed is very slow aswell (1KBit/s at worst).
Deutsche Telekom in Germany aswell. Additionally, downloading those files through a us proxy, for example from hidester.com results in way better download speeds.
[6.12.9] Can't start, update or remove containers - ZFS issue?
in Stable Releases
Posted
Yes, i have thought about that aswell, but i have swapped for other ram and didnt help either. Also according to the linked github issue, others have this issue aswell, on other distro´s, not just unraid