The LinuxServer.io team brings you another container release featuring:

• regular and timely application updates
• easy user mappings (PGID, PUID)
• custom base image with s6 overlay
• weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
• regular security updates

Find us at:

• Blog - all the things you can do with our containers including How-To guides, opinions and much more!
• Discord - realtime support / chat with the community and the team.
• Discourse - post on our community forum.
• GitHub - view the source for all of our repositories.
• Open Collective - please consider helping us by either donating or contributing to our budget

Ddclient is a Perl client used to update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider. It was originally written by Paul Burry and is now mostly by wimpunk. It has the capability to update more than just dyndns and it can fetch your WAN-ipaddress in a few different ways.

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling lscr.io/linuxserver/ddclient:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Edit the ddclient.conf file found in your /config volume (also see official ddclient documentation). This config file has many providers to choose from and you basically just have to uncomment your provider and add username/password where requested. If you modify ddclient.conf, ddclient will automaticcaly restart and read the config.

If ddclient shall fetch the dynamic (public) IP-address from a fritz.box (AVM) add the following line to /config/ddclient.conf:

use=cmd, cmd=/etc/ddclient/get-ip-from-fritzbox

This image can be run with a read-only container filesystem. For details please read the docs.

/tmp must also be mounted to tmpfs for this image.

This image can be run with a non-root user. For details please read the docs.

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

---
services:
  ddclient:
    image: lscr.io/linuxserver/ddclient:latest
    container_name: ddclient
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - /path/to/ddclient/config:/config
    restart: unless-stopped

docker run -d \
  --name=ddclient \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -v /path/to/ddclient/config:/config \
  --restart unless-stopped \
  lscr.io/linuxserver/ddclient:latest

Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__MYVAR=/run/secrets/mysecretvariable

Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable file.

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.

When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id your_user as below:

id your_user

Example output:

uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)

We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

• Shell access whilst the container is running:

  docker exec -it ddclient /bin/bash

• To monitor the logs of the container in realtime:

  docker logs -f ddclient

• Container version number:

  docker inspect -f '{{ index .Config.Labels "build_version" }}' ddclient

• Image version number:

  docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/ddclient:latest

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

• Update images:

  • All images:

    docker-compose pull

  • Single image:

    docker-compose pull ddclient

• Update containers:

  • All containers:

    docker-compose up -d

  • Single container:

    docker-compose up -d ddclient

• You can also remove the old dangling images:

  docker image prune

• Update the image:

  docker pull lscr.io/linuxserver/ddclient:latest

• Stop the running container:

  docker stop ddclient

• Delete the container:

  docker rm ddclient

• Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)

• You can also remove the old dangling images:

  docker image prune

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone https://github.com/linuxserver/docker-ddclient.git
cd docker-ddclient
docker build \
  --no-cache \
  --pull \
  -t lscr.io/linuxserver/ddclient:latest .

The ARM variants can be built on x86_64 hardware and vice versa using lscr.io/linuxserver/qemu-static

docker run --rm --privileged lscr.io/linuxserver/qemu-static --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

• 10.07.25: - Rebase to Alpine 3.22.
• 08.07.24: - Fix cache issue.
• 08.07.24: - Don't copy config from /config/ddclient.conf to /ddclient.conf at runtime.
• 27.06.24: - Rebase to Alpine 3.20.
• 23.12.23: - Rebase to Alpine 3.19.
• 25.08.23: - Rebase to Alpine 3.18.
• 04.07.23: - Deprecate armhf. As announced here
• 13.02.23: - Rebase to Alpine 3.17, migrate to s6v3.
• 20.10.22: - Update build instructions for 3.10.0. Update default ddclient.conf.
• 15.01.22: - Rebase to Alpine 3.15
• 15.05.21: - Distribute script 'sample-get-ip-from-fritzbox' from ddclient repo
• 08.03.21: - Added bind-tools to provide nsupdate
• 01.06.20: - Rebasing to alpine 3.12.
• 08.02.20: - Ingest from Github.
• 06.02.19: - Fix permissions.
• 19.12.19: - Rebasing to alpine 3.11.
• 28.06.19: - Rebasing to alpine 3.10.
• 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
• 10.03.19: - Add perl-io-socket-inet6 for ipv6 support.
• 22.02.19: - Rebasing to alpine 3.9.
• 11.02.19: - Add pipeline logic and multi arch.
• 22.08.18: - Rebase to alpine 3.8.
• 10.08.18: - Update to ddclient v3.9.0. For Cloudflare users, please ensure you remove the line server=www.cloudflare.com from your ddclient.conf.
• 07.12.17: - Rebase to alpine 3.7.
• 28.05.17: - Rebase to alpine 3.6.
• 10.02.17: - Rebase to alpine 3.5.
• 26.11.16: - Update README to new standard and add icon and other small details.
• 29.08.16: - Initial release.