On 19/1/2026 08:12, Christoph Zechner wrote:
On 19/01/2026 09:04, Bruno Manzoni via Xymon wrote:
Why not? One doesn't exclude the other, right? I'm curious to hear both sides. What would be the pros and cons of having a Dockerized server receiving data from native clients? @Scot, why do you think the client wouldn't be viable? @Christoph, why the 'please don't'?
because deployment via Docker is cumbersome and annoying IMO, Docker containers are notoriously unsafe (especially when run by the root user which is the default), hard to isolate network-wise and offer no real advantage here. Deploying xymon in a secure way (with encryption via stunnel for example) takes time and lots of configuration entries, I really don't see how putting the server component into a container would make things better.
Christoph
Well, funny this topic came up, but I have been planning on moving my xymon install to a container in the kubernetes cluster.
Advantages are that I no longer need to ensure the old physical machine is working, any single physical machine failure will allow kubernetes to restart the container on another node. Storage is persistent using the existing k8s storage (network). Of course, cluster failure will mean monitoring failure, and here is where my plan was to simply run a second instance in another cluster (at another location) to monitor the first and vice versa.
As far as isolation, sure, it is possible for an exploit of xymon to result in an exploit on the physical node, and ultimately the entire cluster..... this is a trade-off, the same as all other container based workloads.
I haven't done the work yet, so am not certain that it will work well, but that is my plan.
As for other discussions on new releases, I'd actually suggest to focus on tarball and/or docker releases. Let the distributions pick up the maintained tarball and create their own packages, at least in the short term. That is, focus on creating a stable new release with existing patches, rather than worry about how to create packaged versions.
Just my 0.02c
Regards, Adam
It seems like a good hybrid idea to me, but I’d love to understand your technical concerns!
Bruno
Le 19.01.2026 à 07:20, Christoph Zechner a écrit :
On 19/01/2026 01:22, Scot Kreienkamp wrote:
Would it be worthwhile to create a docker image of xymon? The server could run in docker. The client could not though. Too much information would not be visible to make it a viable solution.
please don't. Why would you do this?
Scot Kreienkamp
*Scot Kreienkamp | Applications Infrastructure Architect | La-Z-Boy Corporate * (734) 384-6403 | 1-734-915-1444 | Scot.Kreienkamp@la-z-boy.com One La-Z-Boy Drive | Monroe, Michigan 48162 | la-z-boy.com <http:// www.la-z-boy.com/> facebook.com/lazboy <http://facebook.com/lazboy> |instagram.com/ lazboy <https://instagram.com/lazboy> |youtube.com/lazboy <http:// youtube.com/ lazboy>
LaZboy Logo
> On Jan 18, 2026, at 4:58 PM, Roland Rosenfeld <roland@spinnaker.de> wrote: > > Hi Mark! > > On Sun, 18 Jan 2026, Mark Felder via Xymon wrote: > >>> It would be great to have a 4.3.31 without architectural changes >>> but with the current painpoints fixed. > >> I agree. I think 4.3.31 as our test run should be a roll up of >> patches collected by distros and other small patches that have been >> floating around which don't risk changing behavior or build >> dependencies. That would exclude the PCRE2 change for this release >> as we don't know how this will affect non-Linux/BSD platforms. It >> should be fine as PCRE2 has been around a long time, but nobody has >> ever tried to build it on e.g., Solaris yet > > But not upgrading to PCRE2 but staying with the old library, which was > last updated 2021-06-22 (8.45) and is now officially "no longer being > actively maintained" (see https://www.pcre.org/ <https:// www.pcre.org/>) means, that RHEL 10 > and Debian 13 (trixie) are no longer supported, since these do no > longer ship the old pcre library. > > BTW: pcre2 was first released in 2015, so I expect that every OS > should be able to build/ship this in more than 10 years. > > I have to admit, that I didn't try this out on Solaris yet, but is > there really anybody running a xymon server on Solaris nowadays? If > you only need the client (with conftype "server"), no pcre is needed > at all (only for the client with conftype "client"), so for most > users, who only need a client on a "special" OS, this shouldn't be an > issue. > > A short search showed me, that pcre2 seems to be available on Solaris > 10 and 11: https://www.opencsw.org/package/pcre2/ <https:// www.opencsw.org/package/pcre2/> (but I didn't try > this out myself, since I'm very happy to have shut down all Solaris > boxes last year and so I no longer have to pray, if one of them hicks > up and nobody is there to fix it). > > Greetings > Roland > > PS: Do you also see my mails on the ML "From: Roland Rosenfeld > <roland@spinnaker.de>"? > While I see most postings in the ML as "From: Some Name as xymon > <xymon@xymon.com>", I see myself (and some others) with their real > addresses (and get DMARC warnings, because the list breaks DKIM > (by adding a signature) and SPF (since the list server isn't > permitted for spinnaker.de)... > _______________________________________________ > Xymon mailing list -- xymon@xymon.com > To unsubscribe send an email to xymon-leave@xymon.com
This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com