Docker ps ancestor filter on image without a tag doesn't work
Open
Nobody has claimed this yet.
area/ux
kind/enhancement
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
338fbd7d54c9 slacgrip/master:191022 "python3 -u run_grid…" 5 minutes ago Up 5 minutes 6266-6299/tcp gridlabd_1_1_recovery_ieee37_with_str_repl.glm_05883fac-f4af-4ee4-80e6-47d38d00843a
When I run: docker ps -a -q --filter ancestor=slacgrip/master, I get no output
If I run:
docker ps -a -q --filter ancestor=slacgrip/master:191022, with the '191022' tag, then it prints the container ID.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the two docker ps -a -q --filter ancestor=... commands from the issue, comparing the untagged and tagged image forms. Trace the ancestor filter entry point in the Docker CLI and determine why the untagged reference returns no container. Done means the untagged command finds the shown container while the tagged behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100