I have a django web app that runs in as three docker images. One is a cronjob, one is the web app and one is the nginx service. I have separate build and deploy areas on the same Ubuntu system I deploy to /opt/dlnWebApplication. I can build the save tars files in the dev rea. I copy the tar file to /opt. Load the tar file and do a docker-compose up -d and everything run like a champ. In case of a system reboot or other oddity, I was trying to find a good way to make sure that the images were restarted. I have a dlnWebApplication.service file, but when I start the service it is currently trying to build the images. It cannot do that as the necessary files are in the build area. Here is my docker-compose.yml file:

I have a django web app that runs in as three docker images. One is a cronjob, one is the web app and one is the nginx service. I have separate build and deploy areas on the same Ubuntu system I deploy to /opt/dlnWebApplication. I can build the save tars files in the dev rea. I copy the tar file to /opt. Load the tar file and do a docker-compose up -d and everything run like a champ. In case of a system reboot or other oddity, I was trying to find a good way to make sure that the images were restarted. I have a dlnWebApplication.service file, but when I start the service it is currently trying to build the images. It cannot do that as the necessary files are in the build area. Here is my docker-compose.yml file: