Replies: 3 comments
-
I'm not aware of any issues with the binary we're shipping. It is validated as part of the process of QAing every release. Perhaps the installation on your node was interrupted and the binary corrupted? |
Beta Was this translation helpful? Give feedback.
-
I see this behavior across 12 different Windows nodes at the moment, so I don't think it's any kind of freak error in the download. I have the ctr.exe on my local machine, if there's a way to get to you. I'm not sure what to look at in it to identify what's wrong. It gives the same error attempting to run it on my Windows 10 machine as on the 2019 Server machines. |
Beta Was this translation helpful? Give feedback.
-
I am also seeing similar behaviour while registering the windows node using Rancher 2.6.10 in one of the customer environment |
Beta Was this translation helpful? Give feedback.
-
Environmental Info:
RKE2 Version:
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
This cluster is created from Rancher Manager 2.7.0, Windows nodes joined by default install.ps1 provided.
Describe the bug:
Running rke2-uninstall.ps1 generates this error:
Steps To Reproduce:
Expected behavior:
Expected the RKE2-Uninstall.ps1 to be able to clean up the node.
Attempting to use the installed ctr.exe executable manually provides the same error - it seems this rke2 version is downloading a non-Windows version of CTR?
Beta Was this translation helpful? Give feedback.
All reactions