Docker-Compose Restart Policy

I looked thru the docs for docker-compose and I see that Version 3 has a deploy restart policy but it’s only for swarm. I tried setting restart_policy on my service but got this error:

ERROR: The Compose file './docker-compose.yml' is invalid because:
Unsupported config option for services.web: 'restart_policy'

Is there any way to set a restart policy on services created using docker-compose outside of a swarm?

  • Creating a Docker container with runable android tool
  • LEMP Kubernetes
  • Docker build ADD vs RUN curl
  • How to delete a label for a kubernetes pod
  • docker spring-boot application accessible only on 172.17 ip
  • Why “git clone” is trying to use https
  • Problems trying to install docker compose on Kubuntu 16.04
  • Cannot exec into docker container due to application
  • Why is Internal memory in java Native Memory Tracking increasing
  • launch basic bash script on docker build from windows system
  • Firefox in a docker container accessible from selenium in another
  • AWS ECS Error when running task: No Container Instances were found in your cluster
  • 2 Solutions collect form web for “Docker-Compose Restart Policy”

    Version 2 supports restart policies, using the restart keyword, and should work fine for you if you don’t need Swarm (which you said you don’t need/want).

    version: '2'
        image: apache
        restart: always

    Compose format version 3 has a parameter called restart_policy, but so far as I can tell from documentation it is only valid as part of deploy, which is only used when deploying to a Swarm. So version 3 is probably not useful in your case.

    It’s looks like a gap in documentation

    In 3rd version we can still use “restart” inside services same as before in v.2 (except for deploy into swarm)

    version: '3'
        restart: on-failure:5 
    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.