This message was deleted.
# generala
adamant-kite-43734
04/21/2026, 8:54 PMThis message was deleted.
c
creamy-pencil-82913
04/21/2026, 9:42 PMcan you show the full error?
creamy-pencil-82913
04/21/2026, 9:43 PMAre you trying to run the kubectl command from a windows node, or another node?
l
limited-elephant-16797
04/22/2026, 3:58 AMRunning from my local machine, macos.
limited-elephant-16797
04/22/2026, 4:03 AMfailed to try resolving symlinks in path "//var/log//pods//default_<pod-name>_xxxx//<container-name>//0.log" : no such file or directory
c
creamy-pencil-82913
04/22/2026, 4:41 AMI don’t think that’s one I’ve seen before. What do you actually have on the node at that path?
creamy-pencil-82913
04/22/2026, 4:42 AMAre there any mounts or other oddities in any of the directories along that path?
l
limited-elephant-16797
04/22/2026, 5:24 AMContainers logs are present at that path, I checked manually, file 0.log is present which contains the logs of the respective container.
limited-elephant-16797
04/22/2026, 6:56 AMNo other mounts
limited-elephant-16797
04/23/2026, 5:02 AMAny suggestions? @creamy-pencil-82913
c
creamy-pencil-82913
04/23/2026, 5:52 AMNo, never seen it before and no ideas what might cause it. Is it on all you nodes or just one?
l
limited-elephant-16797
04/23/2026, 6:05 AMOn all Windows nodes
limited-elephant-16797
04/23/2026, 6:05 AMShould I raise a bug for this? This specifically started occurring after RKE2 upgrade.
c
creamy-pencil-82913
04/23/2026, 6:06 AMSure. Provide all the info you can about the os config, partition layout, and so on.
creamy-pencil-82913
04/23/2026, 6:09 AMWe build containerd, kubelet, and so on all right from upstream source so I'm not really confident it's something that's going to be fixable in rke2 itself, likely to be an upstream issue somewhere
l
limited-elephant-16797
04/23/2026, 6:21 AMOk, let me research if it is an upstream issue. Even if it's upstream, it's impacting RKE2 clusters as well.
9 Views