How to Set Up Docker Container Auto-Restart on Failure in a DigitalOcean Droplet?

Question

I have a few Docker containers running on a DigitalOcean Droplet, and I want to make sure they automatically restart if they crash or encounter an error. I know Docker has some built-in restart policies, but I’m not entirely sure how to configure them properly.

Can someone explain how to set up Docker containers to automatically restart on failure? Also, are there any recommended restart policies for production environments?

Bobby · Accepted Answer

Hi there, I’ve answered a similar question about this here: https://www.digitalocean.com/community/questions/how-to-start-docker-containers-automatically-after-a-reboot Restart Policies :Docker provides several restart policies: no: The container will not be restarted (default behavior). on-failure: Restarts the container if it exits due to an error (non-zero exit code). always: Always restarts the container, regardless of the exit status. unless-stopped: Restarts the container unless you manually stop it. Setting the Restart Policy :When starting a container, you can specify the restart policy with the --restart flag. For example, to set the container to restart on failure, use the following command: docker run --restart on-failure Or, to make the container always restart, use: docker run --restart always Example with Docker Compose :If you’re using Docker Compose, you can configure the restart policy in your docker-compose.yml file like this: version: '3' services: myservice: image: my-image restart: on-failure This will ensure that your service restarts on failure. For most production environments, using --restart always is a good choice to ensure that your container stays running. However, if you’re concerned about containers getting stuck in a crash loop, --restart on-failure is a safer option to only restart the container if it fails due to an error. - Bobby

KFSys · Answer

Heya, Here’s a breakdown of the most common Docker restart policies: Docker Restart Policies no : This is the default policy. Docker will not restart the container automatically. always : Docker will always restart the container if it stops, regardless of the exit status. It will also restart the container when the Docker daemon is restarted or the host machine is rebooted. on-failure : Docker will only restart the container if it exits with a non-zero exit status (i.e., if it crashes). You can also specify a maximum number of restart attempts. unless-stopped : Docker will always restart the container unless it was manually stopped. This is similar to the always policy but will not restart containers that were stopped manually. How to Apply Restart Policies You can set the restart policy when starting a container by using the --restart flag in the docker run command. Here’s how to configure it: For a container to restart on failure : docker run --restart on-failure:5 my-container This example will restart the container up to 5 times if it crashes. For a container to always restart : docker run --restart always my-container For a container to restart unless stopped : docker run --restart unless-stopped my-container Recommended Restart Policies for Production In production environments, the recommended restart policy generally depends on the application and expected behavior: Critical applications : Use always or unless-stopped to ensure that your containers stay up, even if the Docker daemon or server is restarted. Non-critical applications or testing : Use on-failure to limit the number of restarts in case of repeated crashes, which can help avoid potential resource exhaustion or infinite restart loops. Updating Existing Containers To update an existing container with a restart policy, you can do so by modifying the container with the following command: docker update --restart=always my-container This way, you don’t have to recreate the container if it’s already running. By implementing the appropriate restart policy, you can ensure your Docker containers are resilient and can recover from unexpected crashes or errors.

Become a contributor for community

DigitalOcean Documentation

Resources for startups and AI-native businesses

The developer cloud

Start building today

Report this

How to Set Up Docker Container Auto-Restart on Failure in a DigitalOcean Droplet?

Related questions

How to tell if your reverse proxy is buffering your token stream (and why I had to rent a Droplet to find out)

Getting "unauthorized: authentication required" when pushing a docker image

Docker Networking Explained: How Containers Talk to Each Other

What is the best way to learn Docker networking before deploying multi-container apps on a Droplet?

Where do I start with DevOps as a beginner on DigitalOcean?

Where do I start with Docker as a complete beginner?

App Platform Docker builds broken due to no BuildKit

Best way to deploy a small Docker app on DigitalOcean without overengineering?

Registry showing wrong limit

Droplet: Docker => laravel (mysql) + astro app [unusable]

docker laravel app with astro frontend

create droplet with version of ubuntu I want, not what you want

Report this

How to Set Up Docker Container Auto-Restart on Failure in a DigitalOcean Droplet?

Related questions

How to tell if your reverse proxy is buffering your token stream (and why I had to rent a Droplet to find out)

Getting "unauthorized: authentication required" when pushing a docker image

Docker Networking Explained: How Containers Talk to Each Other

What is the best way to learn Docker networking before deploying multi-container apps on a Droplet?

Where do I start with DevOps as a beginner on DigitalOcean?

Where do I start with Docker as a complete beginner?

App Platform Docker builds broken due to no BuildKit

Best way to deploy a small Docker app on DigitalOcean without overengineering?

Registry showing wrong limit

Droplet: Docker => laravel (mysql) + astro app [unusable]

docker laravel app with astro frontend

create droplet with version of ubuntu I want, not what you want