this post was submitted on 28 Nov 2023
25 points (100.0% liked)

Linux

46794 readers
1776 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

Related Communities

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

founded 5 years ago
MODERATORS
 

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'

top 25 comments
sorted by: hot top controversial new old
[–] [email protected] 15 points 9 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.

[–] [email protected] 17 points 9 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.

[–] [email protected] 4 points 9 months ago

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

[–] [email protected] 3 points 8 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.

[–] [email protected] 2 points 8 months ago

i do the exact same

[–] [email protected] 4 points 9 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

[–] [email protected] 7 points 9 months ago

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

[–] [email protected] 5 points 9 months ago (1 children)

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

[–] [email protected] 2 points 9 months ago (1 children)

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

[–] [email protected] 4 points 9 months ago

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

[–] [email protected] 5 points 9 months ago (2 children)

I often just do

docker ps | awk "{print $1}" | xargs docker stop

Add some filtering in there and you're golden

[–] [email protected] 2 points 9 months ago (2 children)

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

[–] [email protected] 5 points 9 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.

[–] [email protected] 2 points 8 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.

[–] [email protected] 2 points 8 months ago

This is what I do as well

[–] [email protected] 2 points 8 months ago (1 children)

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:

podman stop --filter name=foo

man podman-stop tells us:

   --filter, -f=filter
       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
       inclusive with the only exception being label which is exclusive. Filters with different keys always work exclusive.
[–] [email protected] 2 points 8 months ago
Usage:  docker stop [OPTIONS] CONTAINER [CONTAINER...]

Options:
  -s, --signal string   Signal to send to the container
  -t, --time int        Seconds to wait before killing the container

Unfortunately no filter here

[–] xlash123 2 points 8 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.

[–] [email protected] 1 points 9 months ago (1 children)

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

[–] [email protected] 1 points 8 months ago

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

[–] [email protected] 1 points 9 months ago (1 children)

Why create the function _dcl()?

[–] [email protected] 1 points 8 months ago (1 children)

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

[–] [email protected] 1 points 8 months ago

you could instead do:

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

in bashrc or wherever you're setting this up.

[–] [email protected] 1 points 9 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)

[–] [email protected] 1 points 8 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.