Application Setup

• Go to the duckdns website, register your subdomain(s) and retrieve your token.
• Create a container with your subdomain(s) and token. If you own user.duckdns.org, you set SUBDOMAINS=user. You would NOT set a sub subdomain like overseerr from overseerr.user.ducksdns.org.
• It will update your IP with the DuckDNS service every 5 minutes (with a random jitter).

Notice regarding automatic detection

Read-Only Operation

Usage

docker-compose (recommended, click here for more info)

---
services:
  duckdns:
    image: lscr.io/linuxserver/duckdns:latest
    container_name: duckdns
    network_mode: host #optional
    environment:
      - PUID=1000 #optional
      - PGID=1000 #optional
      - TZ=Etc/UTC #optional
      - SUBDOMAINS=subdomain1,subdomain2
      - TOKEN=token
      - UPDATE_IP=ipv4 #optional
      - LOG_FILE=false #optional
    volumes:
      - /path/to/duckdns/config:/config #optional
    restart: unless-stopped

docker cli (click here for more info)

docker run -d \
  --name=duckdns \
  --net=host `#optional` \
  -e PUID=1000 `#optional` \
  -e PGID=1000 `#optional` \
  -e TZ=Etc/UTC `#optional` \
  -e SUBDOMAINS=subdomain1,subdomain2 \
  -e TOKEN=token \
  -e UPDATE_IP=ipv4 `#optional` \
  -e LOG_FILE=false `#optional` \
  -v /path/to/duckdns/config:/config `#optional` \
  --restart unless-stopped \
  lscr.io/linuxserver/duckdns:latest

Parameters

Environment variables from files (Docker secrets)

-e FILE__MYVAR=/run/secrets/mysecretvariable

Umask for running applications

User / Group Identifiers

id your_user

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

Docker Mods

Support Info

• Shell access whilst the container is running:

```bash
docker exec -it duckdns /bin/bash
```

• To monitor the logs of the container in realtime:

```bash
docker logs -f duckdns
```

• Container version number:

```bash
docker inspect -f '{{ index .Config.Labels "build_version" }}' duckdns
```

• Image version number:

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

Updating Info

Via Docker Compose

• Update images:

* All images:

    ```bash
    docker-compose pull
    ```

* Single image:

    ```bash
    docker-compose pull duckdns
    ```

• Update containers:

* All containers:

    ```bash
    docker-compose up -d
    ```

* Single container:

    ```bash
    docker-compose up -d duckdns
    ```

• You can also remove the old dangling images:

```bash
docker image prune
```

Via Docker Run

• Update the image:

```bash
docker pull lscr.io/linuxserver/duckdns:latest
```

• Stop the running container:

```bash
docker stop duckdns
```

• Delete the container:

```bash
docker rm duckdns
```

• 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:

```bash
docker image prune
```

Image Update Notifications - Diun (Docker Image Update Notifier)

Building locally

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

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