Continuous disk IO of "s6-supervise ddclient" process

[phatpaul]

Is there an existing issue for this?

• I have searched the existing issues

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 NginxProxyManager/nginx-proxy-manager#2741
https://github.com/NginxProxyManager/nginx-proxy-manager/pull/3044/files

Steps To Reproduce

Just the normal use case.

Environment

- OS: Ubuntu 20.04
- How docker service was installed: apt install

CPU architecture

arm64

Docker creation

services:
  ddclient:
    image: linuxserver/ddclient
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/New_York
    volumes:
      - ./config/:/config

### Container logs

```bash
Total DISK READ:         0.00 B/s | Total DISK WRITE:         4.87 K/s
Current DISK READ:       0.00 B/s | Current DISK WRITE:       7.31 K/s
    TID  PRIO  USER     DISK READ DISK WRITE>    COMMAND
3250337 be/4 root        0.00 B/s    4.87 K/s s6-supervise svc-ddclient

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[phatpaul]

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

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[LinuxServer-CI]

This issue is locked due to inactivity