Topic: Running WeeWX in a container on a QNAP NAS

[Gyvate]

It seems that the installation process wants to use "tools" that are not available in container environment and craps out without continuing.

For example : nvoke-rc.d: could not determine current runlevel

It's kinda bizarre because much more complicated software can be installed and used. Who ever wrote this installation script for deb, did not bother to test it properly or was just lazy.

the container version of ubuntu is, politically correctly speaking, light-weight.
A RaspberryPi Debian (Buster) is much richer ...

As for the installation - just extract the ZIP file to a temp folder and then copy the Seasons folder over - subdirectory /home/weewx/skins/seasons might need to be created
And then it should run - maybe some skin.conf and weewx.conf adaptions needed for the customized naming of the labels

[BaseLine]

I got the files by doing a python install and then deb install. You see, the /etc/init.d/weewx script is also joke because it cant start weewx, if you used python script for installing it. So, the whole thing is kind of a clusterf**, if you ask me.

bugs:

1) weewx crashes without rsyslogd 
2) install wont finish properly if nvoke-rc.d could not determine current runlevel

[Gyvate]

I got the files by doing a python install and then deb install. You see, the /etc/init.d/weewx script is also joke because it cant start weewx, if you used python script for installing it. So, the whole thing is kind of a clusterf**, if you ask me.

bugs:

1) weewx crashes without rsyslogd 
2) install wont finish properly if nvoke-rc.d could not determine current runlevel

Maybe you should share this insight with Tom Keffer and Gary Roderick in the weewx useer group.
They might create a special and working install script for such docker containers and find a solution for the rsyslog - including maybe just installing it as a dependency for the future ...

[BaseLine]

I got the files by doing a python install and then deb install. You see, the /etc/init.d/weewx script is also joke because it cant start weewx, if you used python script for installing it. So, the whole thing is kind of a clusterf**, if you ask me.

bugs:

1) weewx crashes without rsyslogd 
2) install wont finish properly if nvoke-rc.d could not determine current runlevel

Maybe you should share this insight with Tom Keffer and Gary Roderick in the weewx useer group.
They might create a special and working install script for such docker containers and find a solution for the rsyslog - including maybe just installing it as a dependency for the future ...

They can read it here.

I think I made it clear that I am not going to get a google account.

[Gyvate]

I got the files by doing a python install and then deb install. You see, the /etc/init.d/weewx script is also joke because it cant start weewx, if you used python script for installing it. So, the whole thing is kind of a clusterf**, if you ask me.

bugs:

1) weewx crashes without rsyslogd 
2) install wont finish properly if nvoke-rc.d could not determine current runlevel

Maybe you should share this insight with Tom Keffer and Gary Roderick in the weewx useer group.
They might create a special and working install script for such docker containers and find a solution for the rsyslog - including maybe just installing it as a dependency for the future ...

They can read it here.

I think I made it clear that I am not going to get a google account.

a) the user group can be read in a browser without an email account - and their email addresses are visible 
b) you can send an email from any other account to their accounts without engaging in Google   

[BaseLine]

Update.
If any of you are planning to run the weewx inside a container, you are better off starting all the required services like rsyslog, weewx and your webserver with

Code: [Select]

docker exec from the host. Also, uses hosts crontab.
Plenty of examples out there, how to do it.
 

From your hosts command line:
 

Code: [Select]

$ docker exec container-name /bin/sh /etc/init.d/rsyslog start


[vinceskahan]

I commit crimes against docker architecture by running supervisord to run rsyslogd and weewx in one container, which has worked well for years for me.

Nowadays you can simply make an addition to your weewx.conf to have it log to stdout rather than needing a syslog daemon at all.    See their wiki - https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging#customizing%20-what-gets-logged for details.  Basically just change it to say handlers = console.