How to take actions on multiple docker containers at once

xlash123 , 6 months ago

Just a few shortcuts that may help:

• docker ps is an alias for docker container ls
• as long as it can be uniquely identified, a prefix of the container ID can be used instead of copy pasting the entire ID
• you can use container names instead of IDs
• tab completion works for container names

As someone else suggested though, docker compose is probably best suited for this job, but hopefully this helps in other situations.

Shareni , 6 months ago

I’m using docker packages for Doom Emacs. The main one is docker.el. On top of being faster and easier to use than the cli, you can also do some pretty neat stuff like use dired+tramp to browse files and open them in Emacs.

kwozyman , 6 months ago

I don’t know if this works in docker (usually there is 1:1 equivalency between the two), but with podman you can do something like:

<span style="color:#323232;">podman stop --filter name=foo
</span>

man podman-stop tells us:

<span style="color:#323232;">   --filter, -f=filter
</span><span style="color:#323232;">       Filter what containers are going to be stopped.  Multiple filters can be given with multiple uses of the --filter flag.  Filters with the same  key  work
</span><span style="color:#323232;">       inclusive with the only exception being label which is exclusive. Filters with different keys always work exclusive.
</span>

luthis OP , 6 months ago

<span style="color:#323232;">Usage:  docker stop [OPTIONS] CONTAINER [CONTAINER...]
</span><span style="color:#323232;">
</span><span style="color:#323232;">Options:
</span><span style="color:#323232;">  -s, --signal string   Signal to send to the container
</span><span style="color:#323232;">  -t, --time int        Seconds to wait before killing the container
</span>

Unfortunately no filter here

MangoPenguin , 6 months ago

My better way is just using Portainer, select some containers and hit the stop button.

luthis OP , 6 months ago

If I eventually get around to using a GUI, I’ll check out portainer

FishFace , 6 months ago

Why create the function _dcl()?

luthis OP , 6 months ago

I needed a way to pass an argument into the command so it can be used in name=“$1”

FishFace , 6 months ago

you could instead do:

<span style="color:#323232;">dcl() { docker container ls -aq -f name="$1" }
</span>

in bashrc or wherever you’re setting this up.

hanke , 6 months ago

I often just do

<span style="color:#323232;">docker ps | awk "{print $1}" | xargs docker stop
</span>

Add some filtering in there and you’re golden

MangoPenguin , 6 months ago

How tf do you remember that lol, I’m always amazed by CLI focused people being able to remember so much!

hanke , 6 months ago

I think it has to do with creativity!

The CLI tools are just small simple tools. The power comes from having the understanding of how each tool works and how they can be combined.

I don’t remember this string of commands, I know docker, awk and xargs. When I need this, that is the solution I always end up with.

luthis OP , 6 months ago

Dude, I use the CLI all day, every day and I can’t freakin remember half the commands I need.

If it’s something I use often, I’ll make an alias even if it’s just so I can run ‘alias’ in the terminal to get a list of things I use often.

crmsnbleyd , 6 months ago

This is what I do as well

knfrmity , 6 months ago

You can use the container names to address containers. Whether this is a randomly generated name (docker run… with no --name flag), the compose working dir and service name, or the compose container_name var.

I also rarely use the container command. docker is sufficient, or docker compose … while in the working dir of a given compose stack.

this_is_router , 6 months ago

This works but I’d just create a function and use that instead of creating an alias that creates a function and then calls itself.

if your containers are created with a docker compose file you can use docker-compose to target them all

luthis OP , 6 months ago

Is there a way to do this without cd-ing to the directory with the compose file first?

JASN_DE , 6 months ago

You can use -f /path/to/compose.yaml to call it from wherever you like.

RagingToad , 6 months ago

If the containers are related you could use docker-compose, which has commands to stop / restart/ remove all containers at once.

luthis OP , 6 months ago

Cool, didn’t know that!

Just tested, so you have to cd to the directory with the docker-compose.yml file in it first

gratux , 6 months ago

you can also use the -f option to specify the compose file without going to it.

wcooley , 6 months ago

I use Compose even when I have a single container to run because I can put all the config bits I need into a file and can then do most of the work without remembering lots of command line options and often without even needing to mention the service name directly.

youngGoku , 6 months ago

Same. I can’t remember the last time I started a docker container without a compose file.

YIj54yALOJxEsY20eU , 6 months ago

I keep a docker directory in my home dir that has a directory for each docker container/stack in a compose file. Taking down a container looks like so.

• cd docker/wallabag
• docker-compose down

Imo, the best way to work with docker.

Discover5164 , 6 months ago

i do the exact same

luthis OP , 6 months ago

You can of course do it this way too, it’s just extra typing:

docker container stop $(docker container ls -qf name=snikket)