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/dd8d9bc1-77ec-43f9-a2c2-9a06ac9580bcn%40googlegroups.com.
