Description
Description
The daemon.json file does not take effect.
daemon.json configures the following content.
{
"proxies": {
"default": {
"httpProxy": "http://127.0.0.1:7890",
"httpsProxy": "http://127.0.0.1:7890",
"noProxy": "localhost, 127.0.0.1"
}
}
}
Version
colima version 0.6.9
git commit: c3a31ed
runtime: docker
arch: aarch64
client: v26.1.4
server: v26.1.1
qemu-img version 9.0.0
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers
limactl version 0.22.0
Operating System
- macOS Intel <= 13 (Ventura)
- macOS Intel >= 14 (Sonoma)
- Apple Silicon <= 13 (Ventura)
- Apple Silicon >= 14 (Sonoma)
- Linux
Output of colima status
INFO[0000] colima is running using QEMU
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/{UserName}/.colima/default/docker.sock
Reproduction Steps
1.modify the daemon.json file to configure docker proxy
2.colima stop and colima start
3.after colima start, it is found that the proxy configured in daemon.json is not effective
Expected behaviour
After configuring docker proxy in daemon.json, the proxy should be used directly. However, when docker search or docker pull, it always shows proxyconnect tcp: dial tcp 127.0.0.1:7890: connect: connection refused.
Specific commands.
docker search mysql
> Error response from daemon: Get "https://index.docker.io/v1/search?q=mysql&n=25": proxyconnect tcp: dial tcp 127.0.0.1:7890: connect: connection refused
docker pull mysql
> Using default tag: latest
> Error response from daemon: Get "https://registry-1.docker.io/v2/": proxyconnect tcp: dial tcp 127.0.0.1:7890: connect: connection refused
Additional context
No response