Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Latest commit 5869a48 Apr 20, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github update image link Oct 5, 2016
root Pipeline (#10) Oct 15, 2018
.dockerignore add .ignores and templates Sep 17, 2016
.gitignore add .ignores and templates Sep 17, 2016
Dockerfile.aarch64 Switching to new Base images, shift to arm32v7 tag. Mar 23, 2019
Dockerfile.armhf Switching to new Base images, shift to arm32v7 tag. Mar 23, 2019
Jenkinsfile Switching to new Base images, shift to arm32v7 tag. Mar 23, 2019 Switching to new Base images, shift to arm32v7 tag. Mar 23, 2019
jenkins-vars.yml fix jenkins-vars Dec 10, 2018
package_versions.txt Bot Updating Package Versions Apr 20, 2019

The 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 ecosystem to minimise space usage, down time and bandwidth
  • regular security updates

Find us at:

  • Discord - realtime support / chat with the community and the team.
  • IRC - on freenode at Our primary support channel is Discord.
  • Blog - all the things you can do with our containers including How-To guides, opinions and much more!


Docker Pulls Docker Stars Build Status

Duckdns is a free service which will point a DNS (sub domains of to an IP of your choice. The service is completely free, and doesn't require reactivation or forum posts to maintain its existence.


Supported Architectures

Our images support multiple architectures such as x86-64, arm64 and armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling linuxserver/duckdns 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:

Architecture Tag
x86-64 amd64-latest
arm64 arm64v8-latest
armhf arm32v7-latest


Here are some example snippets to help you get started creating a container.


docker create \
  --name=duckdns \
  -e PUID=1000 `#optional` \
  -e PGID=1000 `#optional` \
  -e TZ=Europe/London \
  -e SUBDOMAINS=subdomain1,subdomain2 \
  -e TOKEN=token \
  -e LOG_FILE=false `#optional` \
  -v </path/to/appdata/config>:/config `#optional` \
  --restart unless-stopped \


Compatible with docker-compose v2 schemas.

version: "2"
    image: linuxserver/duckdns
    container_name: duckdns
      - PUID=1000 #optional
      - PGID=1000 #optional
      - TZ=Europe/London
      - SUBDOMAINS=subdomain1,subdomain2
      - TOKEN=token
      - LOG_FILE=false #optional
      - </path/to/appdata/config>:/config #optional
    restart: unless-stopped


Container images 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.

Parameter Function
-e PUID=1000 for UserID - see below for explanation
-e PGID=1000 for GroupID - see below for explanation
-e TZ=Europe/London Specify a timezone to use EG Europe/London
-e SUBDOMAINS=subdomain1,subdomain2 multiple subdomains allowed, comma separated, no spaces
-e TOKEN=token DuckDNS token
-e LOG_FILE=false Set to true to log to file (also need to map /config).
-v /config Used in conjunction with logging to file.

User / Group Identifiers

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 user as below:

  $ id username
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)

You only need to set the PUID and PGID variables if you are mounting the /config folder


Application Setup

  • Go to the duckdns website, register your subdomain(s) and retrieve your token
  • Create a container with your subdomain(s) and token
  • It will update your IP with the DuckDNS service every 5 minutes

Support Info

  • Shell access whilst the container is running: docker exec -it duckdns /bin/bash
  • To monitor the logs of the container in realtime: docker logs -f duckdns
  • container version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}' duckdns
  • image version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/duckdns

Updating Info

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), 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:

Via Docker Run/Create

  • Update the image: docker pull linuxserver/duckdns
  • Stop the running container: docker stop duckdns
  • Delete the container: docker rm duckdns
  • Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
  • Start the new container: docker start duckdns
  • You can also remove the old dangling images: docker image prune

Via Taisun auto-updater (especially useful if you don't remember the original parameters)

  • Pull the latest image at its tag and replace it with the same env variables in one shot:
    docker run --rm \
    -v /var/run/docker.sock:/var/run/docker.sock taisun/updater \
    --oneshot duckdns
  • You can also remove the old dangling images: docker image prune

Via Docker Compose

  • Update all images: docker-compose pull
    • or update a single image: docker-compose pull duckdns
  • Let compose update all containers as necessary: docker-compose up -d
    • or update a single container: docker-compose up -d duckdns
  • You can also remove the old dangling images: docker image prune


  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
  • 22.02.19: - Rebasing to alpine 3.9.
  • 08.02.19: - Update readme with optional parameters.
  • 10.12.18: - Fix docker compose example.
  • 15.10.18: - Multi-arch image.
  • 22.08.18: - Rebase to alpine 3.8.
  • 08.12.17: - Rebase to alpine 3.7.
  • 28.05.17: - Rebase to alpine 3.6.
  • 09.02.17: - Rebase to alpine 3.5.
  • 17.11.16: - Initial release.
You can’t perform that action at this time.