docker image filter command gives random disordered output
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
MacOS 13.6
docker desktop
Version 2.2.0.5 (43884)
Engine: 19.03.8
I have a set of images built 9 hours ago AND IN SAME ONE HOUR, and run cmd to filter them:
$docker image ls -aq -f "since=dda"
output:
9c20f30b4d05
0664d2f7ccc7
55fc44b46332
c3d54aa34790
d6d97e15c7fe
054248ecd094
7543301b7a3f
54d44f445f7e
8190cf14321d
eb793c48e22d
5bb532623497
7f162c8fe68b
9fd81be5f756
but the output sequence is radom, so after run with:
$docker image ls -aq -f "since=dda" "before=054"
7543301b7a3f
c3d54aa34790
d6d97e15c7fe
54d44f445f7e
8190cf14321d
eb793c48e22d
5bb532623497
9fd81be5f756
7f162c8fe68b
obviously the d6d97e15c7fe and more are not belong to the "before filter" sequence, the sequence queue disordered, I found docker image filter can not distinguish between "minutes and seconds", docker CLI might not identify time granularity level else.
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
Start by reproducing the docker image ls -aq -f "since=dda" and combined since/before commands described in the issue, using images created within the same hour. Trace the Docker CLI image-filter entry point and its timestamp handling. Done means the before filter consistently excludes images outside the intended time range.
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
- 35/100