by Admin_P » Wed Mar 22, 2023 8:49 am
Hi! While I understand your disappointment, I have to point out that it's somewhat misdirected - we are neither the original author nor the maintainer for the container in question. So, when the container isn't keeping up with Xeoma's updates, there isn't really much we can do on our end without opening a whole new branch of development and testing effort directed on just one container. As you can see, that wouldn't be very prudent in terms of resource allocation, so we cannot justify doing that. Nevertheless, the support team is willing to look into this subject, despite having every reason to dismiss this as something going well beyond the support's normal scope.
All that said, if stability is the critical factor for your surveillance system, then there is a fairly simple way of achieving it - find the version of Xeoma and the build of the container that works for you and "freeze" it (i.e. keep it exactly as is, without changing/updating anything).
P.S. You may also want to keep in mind that the forum's purpose is to serve as a platform for Xeoma users to exchange their experiences, not to contact Xeoma's support team.