Vince/Tom: Actually I built my own image. It essentially builds weewx via python setup.py and I add a few popular extensions (mqtt, forecast, belchertown) as a "batteries include" release.
My docker image performs all of it's logging to stdout, so you can review the logs in your favorite orchestration tool (eg. I use portainer). My docker image also supports MySQL/MariaDB connections if needed. I will create a public repo with my weewx docker setup. I will post back here with a link and I will write a wiki article about it. My biggest challenge is that my in laws are staying with us and I have kids camping out in my office, so access to my workstation is limited until this week is over. So please be patient until I get a chance to post it. :) Doug Jenkins Largoweather.com On Wed, Nov 23, 2022, 7:21 AM t...@tom.org <t...@tom.org> wrote: > Re the Docker image, Vince is right that it did not support anything but > what I was using, which is x86-64 (I run my instances as Kubetnetes pods). > Now it supports arm, arm64, and x86-64. > > Phusion is a weird base image, but it did a nice job of supporting the > logging requirements of weewx. I would love a collaborator to either > optimize this one or base it on another base altogether. I think Doug is > working on something? > > On Tuesday, November 22, 2022 at 1:47:01 PM UTC-5 vince wrote: > >> Thanks for the explanation. Doug+I are doing the same thing. >> Suppressing LOOP via removing StdPrint and redirecting logging using the v4 >> logging to console as you documented for the wiki in the spring. >> Difference is I'm building up from base debian as a starting point. >> >> [...tl;dr...] >> >> Doug's stuff has more dominos that have to be lined up to build the >> image. He builds on top of Tom Mitchell's image, which builds on top of an >> old pfusion base image, which has some uniquenesses in there for Docker if >> I remember from poking around a bit. I think pfusion is released for less >> architectures too if I remember. I had to rebuild the whole stack starting >> with pfusion when I was trying 64-bit Ubuntu and 64-bit RaspiOS on a pi >> earlier this year and tried to build some Docker images on top of those >> os. Took a while. >> >> Results from a weewx perspective are the same once you get there of >> course, but I wanted a simpler path to updating the os under the hood and >> for playing around with switching the Docker host os version >> (RaspiOS/Ubuntu) and 32/64 bit variants of the host os. Change one line in >> the Dockerfile and go for changing the weewx image os too. Gotta love >> containers. >> >> On Tuesday, November 22, 2022 at 5:07:41 AM UTC-8 Tom Keffer wrote: >> >>> StdPrint is sending messages directly to stdout via print() statements >>> --- the logging facility is not involved at all. So, no, I would not expect >>> that to work. >>> >>> Doug is using a log handler that sends log messages to "console," that >>> is, stdout. So, what you're looking at is a mixture of print() statements >>> and logging messages. >>> >>> Hope that helps. >>> >>> >>> >>> On Mon, Nov 21, 2022 at 5:09 PM vince <vince...@gmail.com> wrote: >>> >>>> Sorry for the late reply. Rebuilding/consolidating my docker setups >>>> and had a question... >>>> >>>> Removing StdPrint 'does' work for suppressing the LOOP messages in >>>> Docker, but is there a way to get the same effect via a custom [Logging] >>>> stanza ? >>>> >>>> I got very lost under the hood trying to follow how StdPrint is logging >>>> at all. >>>> Would this be expected to work ? >>>> >>>> [Logging] >>>> [[loggers]] >>>> [[[weewx.engine.StdPrint]]] >>>> level = ERROR >>>> >>>> >>>> On Sunday, March 27, 2022 at 4:28:52 AM UTC-7 Tom Keffer wrote: >>>> >>>>> Just remove "StdPrint" from the list of reporting services to be run. >>>>> So, this >>>>> >>>>> report_services = weewx.engine.StdPrint, weewx.engine.StdReport >>>>> >>>>> becomes this >>>>> >>>>> report_services = weewx.engine.StdReport >>>>> >>>>> >>>>> On Sun, Mar 27, 2022 at 4:24 AM Doug Jenkins <do...@dougjenkins.com> >>>>> wrote: >>>>> >>>>>> Is there a way to suppress the LOOP data? >>>>>> >>>>> -- >>>> >>> You received this message because you are subscribed to the Google >>>> Groups "weewx-user" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to weewx-user+...@googlegroups.com. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/weewx-user/d1e72f8a-5a6d-4a90-8df5-4722c38a544dn%40googlegroups.com >>>> <https://groups.google.com/d/msgid/weewx-user/d1e72f8a-5a6d-4a90-8df5-4722c38a544dn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- > You received this message because you are subscribed to the Google Groups > "weewx-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to weewx-user+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/d3d194db-8689-4f8b-a293-6952435fa1a3n%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/d3d194db-8689-4f8b-a293-6952435fa1a3n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CACC0i0wnsXF4y_cmRSjjE9H%3Du1fwk89G6-OEV8C4sv5jKiZG1g%40mail.gmail.com.
