Open sigboom opened 9 months ago
one dfdaemon console log file dfdaemon.log What logs do I need to provide?
Check whether the config_path in the containerd configuration is correct, refer to https://github.com/containerd/containerd/blob/main/docs/cri/config.md#registry-configuration.
If correct, please check the containerd log. Why is mirror not used?
Check whether the config_path in the containerd configuration is correct, refer to https://github.com/containerd/containerd/blob/main/docs/cri/config.md#registry-configuration.
If correct, please check the containerd log. Why is mirror not used?
I found it!This is default config in ACK /etc/containerd/config.toml. The default configuration of ACK is missing an "s"
What happens next is up to the community to handle the situation.
dragonfly/templates/dfdaemon/dfdaemon-daemonset.yaml
It is recommended to read config_path from the current node and not hardcode it in the deployment script.
What happens next is up to the community to handle the situation.
dragonfly/templates/dfdaemon/dfdaemon-daemonset.yaml
It is recommended to read config_path from the current node and not hardcode it in the deployment script.
@sigboom Agree!
Bug report:
k8s version is 1.26, containerd version is 1.6.20, dragonfly helm package verison is 1.1.29
Expected behavior:
How to reproduce it:
Using Helm to Deploy on ACK Cluster
Environment:
uname -a
): Linux testompub-pub-172.17.29.36static 5.10.112-11.2.al8.x86_64 #1 SMP Mon Aug 1 20:06:08 CST 2022 x86_64 x86_64 x86_64 GNU/Linux