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.
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 following:
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:
Simply run docker-compose up && docker-compose rm -fsv
🙂
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.
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
我不确定我是否理解, docker-compose run --user 是一个选项,并且 docker-compose.yml 支持用户密钥( http://docs.docker.com/compose/yml/#working95dir-entrypoint-用户主机名-域名-mem95limit-privileged-restart-stdin95open-tty-cpu95shares )。
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.