You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 27, 2023. It is now read-only.
2021-03-29 12:31:32.363 INFO sign:1 : using config: {"registry_mirror":{"remote":"https://index.docker.io","certs":null,"insecure":true,"direct":false},"proxies":[{"regx":"blobs/sha256.*","use_https":false,"direct":false,"redirect":""},{"regx":"testrea","use_https":false,"direct":false,"redirect":""}],"hijack_https":null,"port":65001,"hostIp":"127.0.0.1","certpem":"","keypem":"","verbose":false,"maxprocs":4,"dfget_flags":["--node","supernode:8002=1"],"supernodes":null,"ratelimit":"20MB","workHome":"/root/.small-dragonfly","localrepo":"/root/.small-dragonfly/dfdaemon/data","dfpath":"/opt/dragonfly/df-client/dfget","logConfig":{"maxSize":0,"maxBackups":0,"path":""},"localIP":"","peerPort":0,"streamMode":false}
All other fields are correct. Only registry_mirror.remote is not what I set in dfdaemon config
Ⅲ. Describe what you expected to happen
registry_mirror.remote field in the log should be docker.abctest.com as I set in the configuration file instead of https://index.docker.io
Ⅳ. How to reproduce it (as minimally and precisely as possible)
use the following yaml to create a daemonset, and see logs in container
Ⅰ. Issue Description
dfdaemon fails to read registry_mirror.remote from config
Ⅱ. Describe what happened
the dfdaemon config yaml in the container
bash-4.4# cat /etc/dragonfly/dfdaemon.yml
and what I saw in the dfdaemon log
All other fields are correct. Only registry_mirror.remote is not what I set in dfdaemon config
Ⅲ. Describe what you expected to happen
registry_mirror.remote
field in the log should bedocker.abctest.com
as I set in the configuration file instead ofhttps://index.docker.io
Ⅳ. How to reproduce it (as minimally and precisely as possible)
use the following yaml to create a daemonset, and see logs in container
Ⅴ. Anything else we need to know?
Ⅵ. Environment:
uname -a
):The text was updated successfully, but these errors were encountered: