Adam: Sorry for the late reply. I am still adjusting my gmail filters to get all the weewx-users and weewx-developer messages through.
I ran into the same problem when I started using the docker image for my custom install. I wanted to bring in a few of the popular weewx extensions (MQTT, Belchertown, Windy) yet if I recreate the container, I would have to manually re-add these extensions and then post my weewx.conf back into the solution. This can be a problem when you have to reboot the server for maintenance. So going back to my notes and repo internally, what I did was to create my own docker image using Tom Mitchell's image, then loading the extensions and then copying my weewx.conf file back AFTER the extensions were installed. I also updated his executing script (/bin/run) to point the weewx.conf file to a specific folder (/home/weewx/config/weewx.conf). This way I can make changes to the weewx.conf, redeploy the solution, rebuild the image, etc. To help understand all of this (as this took some time to set up as I was learning docker), I created a public github repo that has all of these files and configurations set so you can see how I set up my station. All of the sensitive items have been removed, so you will need to go through the config files and update them for your station. here is that link : WeeWX Docker Stack Example (NGINX | MQTT | WEEWX | MARIADB) <https://github.com/djenk41us/weewx-docker-stack> Please let me know if this helps and let me know the next issue that you run into. DDJ On Thu, Feb 17, 2022 at 8:25 PM Adam Morgan <muchgooder....@gmail.com> wrote: > @DougJenkins I am hoping that you might be able to see what I am doing > wrong. I can see that the config files are being written inside the docker > container and not the path in /AppData. The weird thing is that it does > create the WeeWx folder in AppData but it is empty. > > https://hub.docker.com/r/mitct02/weewx > > The documentation is for docker run and thus it isn't the same thing: > > docker run -d --volume /Users/tom/weewx.conf:/home/weewx/weewx.conf > --volume > > I did try this - I ended up with a subfolder of "weex.conf" that was again > empty. > > > > On Wednesday, February 16, 2022 at 9:27:07 AM UTC-5 Adam Morgan wrote: > >> Do you see anything wrong in the config that I posted yesterday? >> >> Here is the view from putty: >> >> >> >> On Tuesday, February 15, 2022 at 9:24:51 PM UTC-5 vince wrote: >> >>> Wild guess is that you either tried to map to directories that don't >>> exist, or your volume mounts aren't working. >>> >>> >>> -- > 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/7f7a2556-0ba4-4a86-80bb-7c3a120dd335n%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/7f7a2556-0ba4-4a86-80bb-7c3a120dd335n%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/CACC0i0zSvRmGg9hVpQPbzn9yaOaM-Ri4AOBW3s3Arsz4uLn1Wg%40mail.gmail.com.
