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’

  • Wil Cooley@lemmy.worldEnglish
    17·
    7 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.

    • Goku@lemmy.world
      4·
      7 months ago

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

    • YIj54yALOJxEsY20eU@lemm.ee
      3·
      7 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.