docker-compose restart container if service is dead

docker-compose docker-container
Thomas picture Thomas · Jul 14, 2016 · Viewed 12.1k times · Source

Is it possible to restart container in docker-compose if service that is running inside it returns exit code different than 0? docker-compose.yml option restart: always doesn't work that way. Is there any way to solve it or is this a service issue and I should look for the answer inside of the container?

I use supervisord but adding option autorestart=true doesn't work even if service crashes with exit code 255 - the RUNNING_PID file (created by system) is not being deleted.

Thanks for any reply.

Answer

Gergely Toth picture Gergely Toth · Jul 14, 2016

restart: always will restart the container regardless of the exit code, so even if exit code of the process running inside the container is 0. I'm using restart: on-failure and it does exactly what you describe. It restarts the container on a non zero exit code of the process. After the process exits and it is not restarted you can check the exit code using docker-compose ps

Related questions

How to rebuild docker container in docker-compose.yml?

There are scope of services which defined in docker-compose.yml. These service have been started. I need to rebuild only one of these and start it without up other services. I run the following commands: docker-compose up -d # run all …

Read More
docker-compose creating multiple instances for the same image

I need to start multiple containers for the same image. If i create my compose file as shown below, it works fine. version: '2' services: app01: image: app app02: image: app app03: image: app app04: image: app app05: image: …

Read More
Couldn't connect to Docker daemon at http+docker://localhost with docker-compose

I have this React app that I want to run on an Apache HTTP Docker container. So I created a Dockerfile that works with sudo docker build and sudo docker run <name> FROM httpd:2.4 COPY ./dist/ /usr/local/…

Read More