I have a docker-compose project using Docker for Mac that autostarts when I boot the computer.
I usually start the project with docker-compose up -d, but even running docker-compose stop before shutting down autostarts it again on boot.
I am not aware of specifically enabling this. How can I disable it?
Today I had the same issue that all containers are started when I boot my dev laptop, as restart: always was set in the .yml files.
As I don't want to touch the .yml files, I just found out (thx Bobby) how to alter this setting by:
docker update --restart=no <MY-CONTAINER-ID> 
.yml/or the project somehow :P
docker inspect --format='{{.HostConfig.RestartPolicy.Name}}' <MY-CONTAINER-ID>
restart: no is default mode. There is line inside your docker-compose file with restart: no or restart: unless-stopped. It also means that when you boot your system, it (re)starts container(s) again as long as docker daemon. Details
You need to change restart to no or on-failure, example:
version: '2.1' services: backend: restart: on-failure build: args: USER_ID: ${USER_ID} context: codebase/namp-backend dockerfile: Dockerfile.dev ports: - "5001:5001" - "5851:5851" volumes: - ./codebase/namp-backend:/codebase environment: Also docker-compose down for most cases, gives you the same result - do not start containers while (docker) system startup, except: containers will be deleted after this, not stopped.
Try with docker-compose down instead of docker-compose stop
Stops containers and removes containers, networks, volumes, and images created by up. Networks and volumes defined as external are never removed.
Stops running containers without removing them. They can be started again with docker-compose start.
docker-compose down will destroy all data, The best way is to as #davey said docker update --restart=no <MY-CONTAINER-ID>Use the following command if you want to disable autostart after stopping a specific container:
docker update --restart=no <MY-CONTAINER-ID> If you want to apply this setting to all registered containers, this is the best option:
docker update --restart=no $(docker container ls -a -q) Thank you
docker container ls -a to check containers names & ids and docker inspect --format='{{.HostConfig.RestartPolicy.Name}}' <nameOrId> to check their current settingBeside setting restart: unless-stopped, remove existing containers and recreate them.
docker-compose down docker-compose up -d Now, it would work as expected:
docker-compose stop sudo service docker restart docker-compose ps # should NOT HAVE containers running docker-compose up -d sudo service docker restart docker-compose ps # should HAVE containers running Just an addition to @Hudson Van-dal comment if you are really using compose. When you are in .yml compose file directory you can use:
docker update --restart=no $(docker compose ps -a -q) It will filter out only containers running under this particular compose instead of all available containers.
restart: alwaysin it. If there is, then try changing it torestart: unless-stopped.restart: always. I will change it and see what happens.restart: unless-stoppedcauses docker to time out on requests (ps,stop,kill). And rebooting still starts all the containers!docker-compose stop, but for medocker-compose downworks like a charm. I tend to pair it with--rmi local, but be careful with that.