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’

  • hanke@feddit.nu
    5·
    11 months ago

    I often just do

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

    Add some filtering in there and you’re golden

      • hanke@feddit.nu
        5·
        11 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.

      • ∟⊔⊤∦∣≶@lemmy.nzOP
        2·
        11 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.