Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add `--no-trunc` and `--all` equivalent options to the CLI config file

Open
#6,673 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker, go
Domain
cli

Research direction

Start with the Docker CLI configuration-files documentation and the docker images command entry point. Determine how global and per-command defaults for --no-trunc and --all should be represented, then verify that supported commands use those defaults without changing unrelated options.

Written by the indexing model from the issue text.

Description

kind/feature status/0-triage
Description

Recently the docker images output was changed. This is annoying to long-time users accustomed to the format at best, and breaking to scripting at worst. Things change, however, and I get that formats need to evolve. However, the new format truncates fields (#6650) and hides images (#6652) by default which I strongly dislike. I prefer to, and often need to see everything. So I'd like to configure my cli to output the way I want, so that way I'm insulated from default changes.

In the Docker CLI docs I see options for formatting: https://docs.docker.com/reference/cli/docker/#configuration-files

However I don't see options to cause commands to default to --no-trunc and --all. I'd like to be able to set these both globally for all commands that support them, and per command like the individual formats.

This will be welcomed by users like me who value stability over features. It will let us pin our outputs the way we want, reducing friction when the CLI team evolves the default command outputs. Thank you!

Dominant language
Go
Stars
6.1k
Forks
2.2k
Avg merge
1d 10h
Merged PRs (30d)
47

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker/cli

All issues in docker/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.