Restart Containers In Docker Compose

The short answer

In Docker Compose, to restart all the containers related to all the services defined in the compose.yaml file of your project at once, you must first navigate to the directory containing that configuration file, then use the docker compose restart command:

 $ docker compose restart

Run in Warp

Note that this command will not rebuild the containers or pull updated images; it will only stop and restart the existing containers.

You can learn more about restarting individual containers by reading our article on how to restart single containers in Docker.

Restarting the containers of one or more services

To restart the containers associated with one or more specific services, you can use the following command:

 $ docker compose restart <service_name …>

Run in Warp

Where service_name … is a list of service names separated by a space character.

For example, this command will restart the containers of the website and api services:

 $ docker compose restart website api

Run in Warp

Restarting containers with a timeout

By default, when executing the docker compose restart command, all the containers associated with the specified services are immediately killed by Compose before being restarted.

To allow these containers to stop gracefully, you can specify a restart delay, called a timeout,  expressed in seconds using the -t flag (short for --timeout):

 $ docker compose restart -t <seconds> [<service_name …>]

Run in Warp

Note that if the containers don't stop within the specified timeout, Compose will forcefully terminate them.

For example, the following command will give 90 seconds to the api service to perform its cleanup tasks and gracefully exit before being restarted by Compose:

 $ docker compose restart -t 90 api

Run in Warp

Easily retrieve these commands using Wrap’s AI Command Suggestions

If you’re using Wrap as your terminal, you can easily retrieve these commands using the Wrap AI Command Suggestions feature:

Entering docker compose restart options in the AI Command Suggestion will prompt a list of docker commands that can then quickly be inserted into your shell by pressing CMD + ENTER.

Rebuilding containers on configuration or image change

To automatically stop, remove, and rebuild all the containers associated with all the services defined in the compose.yaml file whose configuration or image have changed, you can use the docker compose up command:

 $ docker compose up

Run in Warp

Alternatively, if you only want to rebuild the containers associated with specific services, you can use the following syntax instead:

 $ docker compose up <service_name …>

Run in Warp

Where service_name … is a list of service names separated by a space character.

Rebuilding containers without dependencies

By default, when rebuilding a service that depends on other services, the dependent services will also be automatically rebuilt by Compose.

To prevent this behavior and rebuild the desired services only, you can use the docker compose up command with the --no-deps flag as follows:

 $ docker compose up --no-deps <service_name …>

Run in Warp

You can learn more about service dependencies by reading our article on understanding the depends_on property in Docker Compose.

Rebuilding containers forcefully

To rebuild the containers associated with specific services regardless of a configuration or image change, you can use the docker compose up command with the --force-recreate flag as follows:

 $ docker compose up --force-recreate <service_name …>

Run in Warp

Defining the restart policy of containers

In Docker Compose, you can use restart policies to define how your containers should behave in case of termination or failure.

These policies are defined through the restart property and take one of the following values:

• no: The default restart policy. It does not restart the container under any circumstances.
• always: The policy always restarts the container until its removal.
• on-failure: The policy restarts the container if the exit code indicates an error.
• unless-stopped: The policy restarts the container irrespective of the exit code but stops restarting when the service is stopped or removed.

 services:
  <service_name>:
    image: <image_name>
    restart: <policy>

Run in Warp

For example, the following configuration will try to restart the container of the api service for a maximum of 3 times on failure:

 services:
  api:
    build: ./api
    restart: on-failure:3

Run in Warp

You can learn more about restart policies for single containers by reading our article on how to restart a Docker container.

Restarting unhealthy services using a health check

In Docker Compose, the healthcheck property allows you to define a test command to periodically check the health of a container. It is often combined with the restart property to define under which condition a service should restart whenever it becomes unhealthy.

 services:
  <service_name>:
    image: <image_name>
    healthcheck:
      test: <command>

Run in Warp

For example, the following configuration checks whether the container of the webserver service is healthy by sending an HTTP request to the nginx server located at the localhost address:

 services:
  webserver:
    image: nginx
    healthcheck:
      test: "curl -f http://localhost"

Run in Warp

You can learn more about health check by reading our article on understanding the healthcheck property in Docker Compose.