Replies: 3 comments
-
Hi, I'm not sure what you mean by the "dockerfile is run the first time the container is executed," as the dockerfile is only used to build the image that the container loads. Do you have any logs showing the issue? |
Beta Was this translation helpful? Give feedback.
-
Sorry, I'm not using the right terminology, I'm new to using Docker. When I first build the image, everything works fine. If I stop the container, and restart it (either manually or through rebooting the machine its running on) a relaunch of plex says the drives aren't mounted. Also, if I start a shell in the container, all the tools installed by pip at the build phase no longer appear to be present within the container. So I can getting running again by running the pip install -r requirements.txt commands, and then launching plex again. Or, I delete the container and rebuild it. |
Beta Was this translation helpful? Give feedback.
-
Whelp, I figured out my mistake. I created a single stack that launched containers for pd_zurg and plex. Plex depended on pd_zurg launching first, but I had the condition as "started" instead of "service_healthy." Changing to "service_healthy" fixed it. |
Beta Was this translation helpful? Give feedback.
-
When I create a new container, the dockerfile is run the first time the container is executed. Thus, the pip install -r requirements is run. However, if i stop the container and restart it, everything installed by pip is lost. The only way to get the container running correctly again is to delete the container and create it fresh again. How can I have the Dockerfile run each time the container is launched? Unless I'm doing something wrong?
Beta Was this translation helpful? Give feedback.
All reactions