Open phatpaul opened 4 days ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
I noticed the new read-only feature and tried it. That seems to work around the issue. My new docker-compose.yml
services:
ddclient:
image: linuxserver/ddclient
environment:
- PUID=1000
- PGID=1000
- TZ=America/New_York
volumes:
- ./config/:/config
tmpfs:
- /run:exec
- /tmp
read_only: true
Is there an existing issue for this?
Current Behavior
This is the same issue as #57 but that was auto closed and locked. The problem still persists, so why close the issue just because nobody bothered to fix it?
Constant disk write activity for no good reason. I suspect this is what trashed my eMMC flash chip on my SBC. I finally noticed it after migrating to a new SBC that has a disk activity light.
Expected Behavior
This docker could be implemented in a way that doesn't do unecessary writes to storage every second.
There was a similar issue reported on another project. Maybe there's a quick fix that's applicable for this one. Please see https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2741 https://github.com/NginxProxyManager/nginx-proxy-manager/pull/3044/files
Steps To Reproduce
Just the normal use case.
Environment
CPU architecture
arm64
Docker creation