verbose log for docker pull
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Description
i am in China and i set some registry mirrors in daemon.json, and can grep it from docker info
{
"debug": true,
"registry-mirrors": [
"https://mirror.ccs.tencentyun.com",
"https://mirror.baidubce.com",
"https://docker.mirrors.ustc.edu.cn",
"https://hub-mirror.c.163.com"
],
"insecure-registries": ["192.168.1.102:8008"]
}
however when i run docker pull xxxxx, it is very very very slow, i want to know whether a registry mirror is used or which registry mirror is used when pulling.
i tried docker -D --log-level=debug pull supabase/postgres-meta:v0.60.7 or journalctl -f -u docker, but i can't find out what i want to know.
btw, how can i test a fastest registry mirror, or can docker choose a fastest one automatically ?
possible related issues:
#336
#2005
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 with the docker pull command and the debug output from docker -D --log-level=debug pull, then compare it with journalctl -f -u docker and the registry-mirrors shown by docker info. Review related issues #336 and #2005. Done should make the mirror used for a pull observable and clarify how mirror speed selection is handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100