- Minor
I use technitium DNS server.
This used to have a custom UNRAID container profile, but not any more.
So now I install the generic container (as found in Apps with the name "dns-server").
The default configuration does not work as is.
I need to edit it with portainer to change a couple of paths and only then it starts.
This is the change I do:
/mnt/user/appdata/technitium-dnsserver/config /etc/dns/config /mnt/user/appdata/technitium-dnsserver /etc/dns
Both as bind.
Keeping the container out of "auto update", used to work fine.
I updated only manually and could then RE-do the changes.
Else, my whole LAN was left without DNS.
BUT recently (and this is why I post here), the container seems to VANISH!
I suspect maybe when checking (automatically) for updates. Even though I have set it to not auto-update.
I mean, I have it running fine, then after a few hours I discover the container is not there any more!
I have to go to "previous apps", re-add it (will not start like that), re-edit it (now it starts).
This happened twice or three times the last few days!
It is really serious, what can possibly remove the container from docker!?
Previously, even if it tried to auto-update, at least it left me with a non-working but EXISTENT container.
This disappearance thing, is new.
Bonus question: Since the change to a working container is minor. How can I store this and re-use it instead of redoing it all the time? Maybe even be able to re-enable it to auto-update to the CORRECT one?