CODEWITHSUNDEEP
dockerdocker-compose
Fan Cheung
Fan Cheung

Reputation: 11345

Auto remove container with docker-compose.yml

docker-compose run has a flag --rm that auto removes the container after run. I am wondering if theres an equivalent config with docker-compose.yml for a specific service, as one of which services i got in yml is a one off build process which should just output the compile file and disappear itself.

Upvotes: 172

Views: 168717

Answers (5)

Willian Carvalho
Willian Carvalho

Reputation: 436

It's been quite some time since this question was posted, but I thought it would be informative to share something that worked for my case, in 2022 :) But keep in mind that this solution still does not remove old containers, as the original author intended to achieve.

docker-compose up --force-recreate -V

In my case, I have a small Redis cluster where I want the data to be completely erased after I stop the servers. Only using --force-recreate didn't do the trick, because the anonymous volume is still reused. That's where -V comes in.

Upvotes: 24

Thomas Gotwig
Thomas Gotwig

Reputation: 4449

Simply run docker-compose up && docker-compose rm -fsv 🙂

👉 https://docs.docker.com/compose/reference/rm

Removes stopped service containers

--force , -f      Don't ask to confirm removal
--stop , -s       Stop the containers, if required, before removing
--volumes , -v    Remove any anonymous volumes attached to containers

alternatively you can do in bash:

#!/bin/bash
set -eux
cleanup() {
    docker compose rm -fsv
}
trap cleanup EXIT
docker compose up

Upvotes: 76

tgogos
tgogos

Reputation: 25142

I haven't found any option to help you define this behavior in the docker-compose.yml file and I think the explanation is the that it will break how some of the docker-compose ... commands are supposed to work.

More on this up/down , start/stop thing:

docker-compose up builds, (re)creates, starts, and attaches to containers for a service.

Since your images are built and the containers of your service have started, you can then use docker-compose stop and docker-compose start to start/stop your service. This is different from docker-compose down which:

Stops containers and removes containers, networks, volumes, and images created by up.

Problem with what you are trying to do:

If you docker-compose up and one of your containers finishes its task and gets (auto)removed, then you can't docker-compose stop and docker-compose start again. The removed container will not be there to start it again.

You might want to take a look at:

Upvotes: 91

Kasper
Kasper

Reputation: 330

My solution to this was to create a little bash script that automatically removes containers afterwards.

If you're on macOS, you can put this script in usr/local/bin. Assuming it's named dco, you can then run chmod +x usr/local/bin/dco to make it executable. On Windows, I have no idea how to get this working, but on Linux it should be similar.

#! /bin/bash

# check for -d, --detached
DETACHED=false
for (( i=1; i <= "$#"; i++ )); do
  ARG="${!i}"
  case "$ARG" in
    -d|--detach)
      DETACHED=true
      break
      ;;
  esac
done

if [[ $1 == "run" ]] && [[ $DETACHED == false ]]; then
    docker-compose run --rm "${@:2}"
elif [[ $1 == "up" ]] && [[ $DETACHED == false ]]; then
    docker-compose up "${@:2}"; docker-compose down
else
    docker-compose "${@:1}"
fi

Edit: Updated the script so that detached mode will work normally, added break to the loop suggested by artu-hnrq

Upvotes: 8

Zehra
Zehra

Reputation: 39

I'm not sure I understand, docker-compose run --user is an option, and the docker-compose.yml supports the user key (http://docs.docker.com/compose/yml/#working95dir-entrypoint-user-hostname-domainname-mem95limit-privileged-restart-stdin95open-tty-cpu95shares).

Upvotes: 1

Related Questions