I've come to realize that an app or docker update has more to do with retrieving the latest image in the repository than it does with updating an XML template from the Community Apps. I noticed this with beryju's repo for Authentik (which is no longer maintained). So, I've simply edited the repo line to point to a later stable version to update the docker image.

This got me thinking - if I continue to simply use the XML created by this "beryju" which isn't even in Community Apps any longer, what happens when later versions' images require additional variables, paths, ports, etc? Is it wise to grab an existing Authentik (in this case) app and have the new one point to my existing appdata folder, paths, ports, etc., so that I know that the XML will be updated?

Does an update to an app even involve updating the XML template ever? As a follow-up question, when an update is shown on the docker page, is this an update only for the image from the repo?

Edited January 1Jan 1 by floepie05
clarity

no, kinda...

so a docker update depends on the docker tag. Most are shipped with latest so when a update is available and if unraid is told to do so it will update.

Things that age and change over time due to updates like the recent immich Postgres v18 tag is changing variables. It is recommended to delete the template and redownload form the CA.


Select your template:

hit the x to delete.



then go to the CA and redownload and install... this will re populate the new template with updated xml.

or edit your exisitng docker.


and add the missing data, paths and new needed stuff. usualy found on the support pages..

3 hours ago, floepie05 said:

I've come to realize that an app or docker update has more to do with retrieving the latest image in the repository than it does with updating an XML template from the Community Apps. I noticed this with beryju's repo for Authentik (which is no longer maintained). So, I've simply edited the repo line to point to a later stable version to update the docker image.

This got me thinking - if I continue to simply use the XML created by this "beryju" which isn't even in Community Apps any longer, what happens when later versions' images require additional variables, paths, ports, etc? Is it wise to grab an existing Authentik (in this case) app and have the new one point to my existing appdata folder, paths, ports, etc., so that I know that the XML will be updated?

Does an update to an app even involve updating the XML template ever? As a follow-up question, when an update is shown on the docker page, is this an update only for the image from the repo?

web UI updates are for docker tages repos only.

if the xml is removed from the CA it was removed for a reason. Thus maintain the tempalte/docker is now on you. I would recommend reusing the temple and change the docker tag to a trusted version or use the new/current model for authentik. (no reason to remove if the docker is still working and getting docker tag updates)

looks like zuerrex is mainting them now for unraid.

This means you would need to use there docker tempatle and tag to get better support on the forum...

xml is never updated you must delete it and redownlad form the CA. as explained above...
example of XML I maintain for the CA
https://github.com/bmartino1/unraid-docker-templates

it can take 2-4 hours after I edit a template before the CA is updated to use one of my xml templates.

I personaly have become more partial to using docker compose. unraid plugin to use compose on unraid...

Many thanks for the great explanations. I think it makes sense to check on my containers then once a year or so for a couple things: a.) whether the template still exists on CA, and b.) if it does exist, compare my current template with the latest template (as well as the repo link or tag for any changes).

Edited January 2Jan 2 by floepie05