Linux

48152 readers

871 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

How to take actions on multiple docker containers at once (lemmy.nz)

submitted 11 months ago by luthis@lemmy.nz to c/linux@lemmy.ml

26 comments fedilink hide all child comments

Again, please tell me if there is a better way to do this.

While testing docker, frequently I need to start/stop/rm containers. I got real sick of having to ls them and copy paste the container ID.

Using this alias, I just have to remember a single part of the name of the container, and I will get the container IDs that can then be included as part of another command:

$ alias dcl='_dcl(){ docker container ls -aq -f name="$1";}; _dcl'

$ dcl snikket
b3fcbc808cc9
1947885fbb24
054d67d2e8b9
d8fe9df5f61f

So now that I'm getting a list of IDs, I can easily, for example, pause all of them:

$ docker container pause $( dcl snikket )
Error response from daemon: container  is not running
Error response from daemon: container  is not running
Error response from daemon: container  is not running
Error response from daemon: container  is not running

The containers weren't actually running, but this shows the alias working.

dcl obviously stands for 'docker container ls'

you are viewing a single comment's thread
view the rest of the comments

[–] RagingToad@feddit.nl 15 points 11 months ago (2 children)

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

[–] wcooley@lemmy.world 16 points 11 months ago (2 children)

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@lemmy.world 4 points 11 months ago

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

[–] YIj54yALOJxEsY20eU@lemm.ee 3 points 11 months ago (1 children)

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@lemm.ee 2 points 11 months ago

i do the exact same

[–] luthis@lemmy.nz 4 points 11 months ago (1 children)

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@lemmy.blahaj.zone 7 points 11 months ago

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