You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+24Lines changed: 24 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,8 @@ TLDR: Multi-arch support is changing from multiple repos to one repo per contain
26
26
[](https://microbadger.com/images/linuxserver/duckdns"Get your own version badge on microbadger.com")
[Duckdns](https://duckdns.org/) 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.
31
33
@@ -35,6 +37,8 @@ TLDR: Multi-arch support is changing from multiple repos to one repo per contain
35
37
36
38
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](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list).
37
39
40
+
Simply pulling `linuxserver/duckdns` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
41
+
38
42
The architectures supported by this image are:
39
43
40
44
| Architecture | Tag |
@@ -43,6 +47,7 @@ The architectures supported by this image are:
43
47
| arm64 | arm64v8-latest |
44
48
| armhf | arm32v6-latest |
45
49
50
+
46
51
## Usage
47
52
48
53
Here are some example snippets to help you get started creating a container.
@@ -111,6 +116,25 @@ Container images are configured using parameters passed at runtime (such as thos
111
116
* image version number
112
117
*`docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/duckdns`
113
118
119
+
## Updating Info
120
+
121
+
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](#application-setup) section above to see if it is recommended for the image.
122
+
123
+
Below are the instructions for updating containers:
124
+
125
+
### Via Docker Run/Create
126
+
* Update the image: `docker pull linuxserver/duckdns`
127
+
* Stop the running container: `docker stop duckdns`
128
+
* Delete the container: `docker rm duckdns`
129
+
* 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)
130
+
* Start the new container: `docker start duckdns`
131
+
* You can also remove the old dangling images: `docker image prune`
132
+
133
+
### Via Docker Compose
134
+
* Update the image: `docker-compose pull linuxserver/duckdns`
135
+
* Let compose update containers as necessary: `docker-compose up -d`
136
+
* You can also remove the old dangling images: `docker image prune`
0 commit comments