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:
- Discord - realtime support / chat with the community and the team.
- IRC - on freenode at
#linuxserver.io. Our primary support channel is Discord. - Blog - all the things you can do with our containers including How-To guides, opinions and much more!
- Podcast - on hiatus. Coming back soon (late 2018).
From August 2018 onwards, Linuxserver are in the midst of switching to a new CI platform which will enable us to build and release multiple architectures under a single repo. To this end, existing images for arm64 and armhf builds are being deprecated. They are replaced by a manifest file in each container which automatically pulls the correct image for your architecture. You'll also be able to pull based on a specific architecture tag.
TLDR: Multi-arch support is changing from multiple repos to one repo per container image.
Duckdns is a free service which will point a DNS (sub domains of duckdns.org) to an IP of your choice. The service is completely free, and doesn't require reactivation or forum posts to maintain its existence.
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.
The architectures supported by this image are:
| Architecture | Tag |
|---|---|
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v6-latest |
Here are some example snippets to help you get started creating a container.
docker create \
--name=duckdns \
-e TZ=Europe/London \
-e SUBDOMAINS=subdomain1,subdomain2 \
-e TOKEN=token \
--restart unless-stopped \
linuxserver/duckdns
-e LOG_FILE=true if you prefer the duckdns log to be written to a file instead of the docker log
-v <path to data>:/config used in conjunction with logging to file
Compatible with docker-compose v2 schemas.
---
version: "2"
services:
duckdns:
image: linuxserver/duckdns
container_name: duckdns
environment:
- TZ=Europe/London
- SUBDOMAINS=subdomain1,subdomain2
- TOKEN=token
mem_limit: 4096m
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 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 |
- 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
- 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
- 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.
