Wow, thank you again Doug! You clearly put a lot of effort into this. Ok, a lot to unpack here. I downloaded your repo into a setup folder on my server and updated .conf with the values that seemed to make sense to me. I already have MariaDB running in another container for Kodi but I left all of that in the docker compose file because in the short term I'll be happy if I can just get this to work. I did add the new user and databases to my existing MariaDB installation, just in case.
I then ran all of your commands by hand. The first was running "docker build ." to initiate the build. I then did each command one by one. That seemed to go well - I see the image and the folders populated as expected. Now what? Should I see a container? I do see the image pulled down and there is a lot of information inside of it that came from the files in your repo. here is the output from the docker build: build . Sending build context to Docker daemon 1.637MB Step 1/9 : FROM mitct02/weewx:4.5.1 4.5.1: Pulling from mitct02/weewx 23884877105a: Already exists bc38caa0f5b9: Already exists 2910811b6c42: Already exists 36505266dcc6: Already exists 07a923053093: Already exists 776b7eaf0a03: Already exists bc700a6f34b5: Already exists 67577fd8c8eb: Pull complete 31df857523bd: Pull complete ecd6e0ddf182: Pull complete bb9aba96460d: Pull complete 3d3e5fc6d05d: Pull complete 6754665d41ef: Pull complete 6135e7b935ea: Pull complete 9b10839751a1: Pull complete 3017c664af94: Pull complete e844a912b1d5: Pull complete 7b5bb4deb379: Pull complete f1c5b3b47d82: Pull complete 7d1f4fb1b49c: Pull complete 7bd1db2eac8f: Pull complete bfc9e864b8db: Pull complete c0191d0c7ecb: Pull complete Digest: sha256:8416c7b57ff50e43538218c8834bdce0238aee0aaaf13dc812148c101862ee9f Status: Downloaded newer image for mitct02/weewx:4.5.1 ---> 92c42aedddc5 Step 2/9 : WORKDIR /home/weewx ---> Running in 5d7735458fe1 Removing intermediate container 5d7735458fe1 ---> 8d4a708a3959 Step 3/9 : ADD config/weewx.conf /home/weewx/ ---> 51a0752dad14 Step 4/9 : ADD extensions/*.zip /home/weewx/extensions/ ---> a0e7a30a9b7e Step 5/9 : ADD bin/run /etc/service/weewx/ ---> 431aa0d66516 Step 6/9 : RUN chmod 755 /etc/service/weewx/run ---> Running in 06d3d16a3ecc Removing intermediate container 06d3d16a3ecc ---> c7cd9bed645c Step 7/9 : RUN ./bin/wee_extension --config=weewx.conf --install /home/weewx/ext ensions/weewx-mqtt.zip ---> Running in 993acec9f543 Request to install '/home/weewx/extensions/weewx-mqtt.zip' Extracting from zip archive /home/weewx/extensions/weewx-mqtt.zip Saving installer file to /home/weewx/bin/user/installer/mqtt Saved configuration dictionary. Backup copy at weewx.conf.20220220133527 Finished installing extension '/home/weewx/extensions/weewx-mqtt.zip' Removing intermediate container 993acec9f543 ---> 29570a351dde Step 8/9 : RUN ./bin/wee_extension --config=weewx.conf --install /home/weewx/ext ensions/weewx-belchertown-master.zip ---> Running in 92413d3b743d Request to install '/home/weewx/extensions/weewx-belchertown-master.zip' Extracting from zip archive /home/weewx/extensions/weewx-belchertown-master.zip Saving installer file to /home/weewx/bin/user/installer/Belchertown Saved configuration dictionary. Backup copy at weewx.conf.20220220133530 Finished installing extension '/home/weewx/extensions/weewx-belchertown-master.z ip' Removing intermediate container 92413d3b743d ---> b9849746c7d4 Step 9/9 : RUN ./bin/wee_extension --config=weewx.conf --install /home/weewx/ext ensions/weewx-windy.zip ---> Running in 98b470bf89fe Request to install '/home/weewx/extensions/weewx-windy.zip' Extracting from zip archive /home/weewx/extensions/weewx-windy.zip Saving installer file to /home/weewx/bin/user/installer/windy Saved configuration dictionary. Backup copy at weewx.conf.20220220133534 Finished installing extension '/home/weewx/extensions/weewx-windy.zip' Removing intermediate container 98b470bf89fe ---> 640a0fa3c5b3 Successfully built 640a0fa3c5b3 root@HAL:/srv/dev-disk-by-label-Docker/AppData/weewx_setup/docker-build# cd .. root@HAL:/srv/dev-disk-by-label-Docker/AppData/weewx_setup# cp docker-build/conf ig/weewx.conf /srv/dev-disk-by-label-Docker/AppData/weewx/config/ root@HAL:/srv/dev-disk-by-label-Docker/AppData/weewx_setup# cp -r skins/* /srv/d ev-disk-by-label-Docker/AppData/weewx/skins/ root@HAL:/srv/dev-disk-by-label-Docker/AppData/weewx_setup# cp mosquitto_mqtt/co nfig/* /srv/dev-disk-by-label-Docker/AppData/weewx/mosquitto/config/ On Sunday, February 20, 2022 at 9:31:08 AM UTC-5 do...@dougjenkins.com wrote: > Essentially yes. I would login with the user account that has docker > access and clone my repo in the current directory (~). Then I would > configure the docker-compose.yml and the weewx.conf files inside my config > folder and use the shell script to build it out. > > You probably have to tinker with the setup as I got this to work on Ubuntu > and not on Debian. > > Also, you do not have to use MariaDB with weewx. I like using MariaDB > because I like to query the live db to run checks and to build a new > interface in the future. > > Let me know where you end up. I am checking my email daily now so I can be > more available to help. > > On Fri, Feb 18, 2022, 10:03 AM Adam Morgan <muchgoo...@gmail.com> wrote: > >> Thank you again Doug! I can't tell you how much I appreciate it. >> >> Ok, I think I got most of what you are saying. So for your example I >> would be copying all of the files in your repo to the /weewx folder on my >> host, modify the yml file, and then execute the config.sh file? >> >> >> >> On Friday, February 18, 2022 at 8:41:09 AM UTC-5 do...@dougjenkins.com >> wrote: >> >>> 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 <muchgoo...@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+...@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 a topic in the >> Google Groups "weewx-user" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/weewx-user/fy3nqJ34Ho0/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> weewx-user+...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/b6283982-ca35-4220-80cd-fa4f770b11e7n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/b6283982-ca35-4220-80cd-fa4f770b11e7n%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/94476b03-0dda-4a58-b3f7-a2b46fbe4db4n%40googlegroups.com.
