calicoctl node diags try to use docker but kubernetes runs with containerd

[Trackhe]

I have a problem with the connection between pods, so i find that site: https://projectcalico.docs.tigera.io/maintenance/troubleshoot/troubleshooting
and tried it out, but when i use 'calicoctl node diags' i get

Collecting diagnostics
Using temp dir: /tmp/calico2622145590
Dumping netstat
Dumping routes (IPv4)
Dumping routes (IPv6)
Dumping interface info (IPv4)
Dumping interface info (IPv6)
Dumping iptables (IPv4)
Dumping iptables (IPv6)
Dumping ipsets
Failed to run command: ipset list
Error: 
Dumping ipsets (container)
Failed to run command: docker run --rm --privileged --net=host calico/node ipset list
Error: 
Copying journal for calico-node.service
Dumping felix stats
Failed to run command: pkill -SIGUSR1 felix
Error: 
Copying Calico logs
Error creating log directory: mkdir /tmp/calico2622145590/diagnostics/logs: file exists

Diags saved to /tmp/calico2622145590/diags-20220219_151350.tar.gz
If required, you can upload the diagnostics bundle to a file sharing service
such as transfer.sh using curl or similar.  For example:

    curl --upload-file /tmp/calico2622145590/diags-20220219_151350.tar.gz https://transfer.sh//tmp/calico2622145590/diags-20220219_151350.tar.gz

but i use the newest version of kubernetes and that runs with containerd. where i activated systemd to. I created the kubelet with systemd too.

Calico version:

Client Version:    v3.22.0
Git commit:        a86e41d02
Cluster Version:   v3.22.0
Cluster Type:      typha,kdd,k8s,operator,bgp,kubeadm

Kubernetes version:

Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.3", GitCommit:"816c97ab8cff8a1c72eccca1026f7820e93e0d25", GitTreeState:"clean", BuildDate:"2022-01-25T21:25:17Z", GoVersion:"go1.17.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.4", GitCommit:"e6c093d87ea4cbb530a7b2ae91e54c0842d8308a", GitTreeState:"clean", BuildDate:"2022-02-16T12:32:02Z", GoVersion:"go1.17.7", Compiler:"gc", Platform:"linux/amd64"}

[lwr20]

This is a straight-up bug. calicoctl can no longer assume that docker is installed on kubernetes nodes.

[mondragonfx]

I have the exact issue as described by OP - any resolution/updates?

[hk135]

Still appears to be here in 3.25.0

[lwr20]

Probably a good first issue if anyone wants to have a go. Calicoctl code is here: https://github.com/projectcalico/calico/tree/master/calicoctl

[jodevsa]

Can I work on this?

[Shuimo03]

hi the issue look not close, Can I try？

[caseydavenport]

@jodevsa @Shuimo03 please do take a look at fixes for this!

[Shuimo03]

ok~

[weironz]

calicoctl node diags has more than one dependency or issue.

1. Dependent Docker
2. Dependent on netstat(net-tools), but ubuntu 22.04 have no net-tools by default, i must run apt install -y net-tools
3. Even if there are no calico log files in the/tmp directory, an error will be reported: Error creating log directory: mkdir /tmp/calico1171669688/diagnostics/logs: file exists
4. Failed to run command: netstat -a -n，although successful on the host, still give Failed error
5. Failed to run command: pkill -SIGUSR1 felix，although successful on the host, still give Failed error

root@node40:~# sudo calicoctl node diags
Collecting diagnostics
Using temp dir: /tmp/calico1171669688
Dumping netstat
Failed to run command: netstat -a -n
Error: 
Dumping routes (IPv4)
Dumping routes (IPv6)
Dumping interface info (IPv4)
Dumping interface info (IPv6)
Dumping iptables (IPv4)
Dumping iptables (IPv6)
Dumping ipsets
Dumping ipsets (container)
Failed to run command: docker run --rm --privileged --net=host calico/node ipset list
Error: 
Copying journal for calico-node.service
Dumping felix stats
Failed to run command: pkill -SIGUSR1 felix
Error: 
Copying Calico logs
Error creating log directory: mkdir /tmp/calico1171669688/diagnostics/logs: file exists

Diags saved to /tmp/calico1171669688/diags-20240428_173830.tar.gz
If required, you can upload the diagnostics bundle to a file sharing service.

[github-actions]

This issue is stale because it is kind/enhancement or kind/bug and has been open for 180 days with no activity.