Yes. I would run docker-compose up and check to see if the docker containers are running. If you are using portainer, check the stack there.
You will know if weewx is working by reviewing the log from the docker container. Again I like using portainer for this as the GUI allows an easy interface to see the results. Common issues that you will run into are permissions to the host directories that weewx/MQTT/NGINX need to access. then the next possible issue would be access to your weather station hardware (assumed you plugged the console to the RPI). You will need to debug this a bit to get it to work properly. if you need to debug the solution, just edit the weewx.conf located in your config folder on the host and restart the containers. Weewx.conf is the main file that governs weewx. DDJ On Sun, Feb 20, 2022 at 4:37 PM Adam Morgan <muchgooder....@gmail.com> wrote: > Sorry, did a private response by mistake a minute ago. I do understand > the basics of docker. This particular approach is a bit new to me so I > thought I would ask what to do next. The config files are in place - is it > a matter of just issuing a docker run with the image? > > On Sunday, February 20, 2022 at 2:53:33 PM UTC-5 vince wrote: > >> On Sunday, February 20, 2022 at 11:15:42 AM UTC-8 muchgoo...@gmail.com >> wrote: >> >>> 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? >>> >> >> You guys might want to consider taking this one offline to email at this >> point, but....... >> >> Tom - I'd suggest you do might some more reading up on Docker.... >> (do https://www.docker.com/101-tutorial - it's pretty good) >> >> - An "image" is a built configured reusable thing. >> - A "container" is a running instance of that image. >> - Building an image ala 'docker build' or 'docker-compose build' does >> not create a running instance (container) of that image. >> - You have to do "docker run' or 'docker-compose up' to start a >> container running. >> - Changes made while building an image persist. >> - Changes made within a running container go 'poof' when the >> container stops >> >> What his scripts are doing is populating an external mounted directory >> under /srv on persistent storage. >> >> But blindly running somebody else's script without spinning yourself up a >> bit more on how Docker works is just going to be confusing and frustrating. >> >> -- > 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/63f503fd-c774-45c9-9690-31c9fc7f3b7bn%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/63f503fd-c774-45c9-9690-31c9fc7f3b7bn%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/CACC0i0yGMaCoT0U6F6ijA%2BVdxiOiW4A4OWi%3DDJLQhRm9UBjb7Q%40mail.gmail.com.
