Efficient way to run a Docker Compose stack in production

Question

I have having some compose files describing a simple Django application which consists of three images and five containers.

What I want is to run this stack in production - to have the whole stack begin on boot, and for containers to restart or be recreated if they crash. There aren't any volumes I care about and the containers won't hold any important state and can be recycled at will.

I am thinking to just put restart: always on all my services and make an init script to do docker-compose up -d on boot.

Is there a recommended way to manage a docker-compose stack in production in a robust way?

Can anyone help me with this query ?

Thanks

Answer 1

Here is a concept which you can follow.Since compose is a client tool, but when you run 

docker-compose up -d, all the container options are sent to the Engine and stored. If you specify restart as always (or preferably unless-stopped to give you more flexibility) then you don't need run docker-compose up every time your host boots.

When the host starts, provided you have configured the Docker daemon to start on boot, Docker will start all the containers that are flagged to be restarted. So you only need to run docker-compose up -d once and Docker takes care of the rest.

I hope the above information will resolve your query.