```curl sfL <https get rke2 io> | INSTALL RKE2 TYPE= server rancher-users #rke2

Title

shy-zebra-53074

09/27/2022, 3:40 PM

curl -sfL <https://get.rke2.io> | INSTALL_RKE2_TYPE="server" INSTALL_RKE2_VERSION="v1.22.15+rke2r1" INSTALL_RKE2_CHANNEL="v1.22" INSTALL_RKE2_CHANNEL_URL="<https://update.rke2.io/v1-release/channels>" sudo -E sh -
[INFO]  using stable RPM repositories
[INFO]  using 1.22 series from channel stable
Rancher RKE2 Common (v1.22)                                                                                                                                                                                                                                  9.7 kB/s | 2.9 kB     00:00    
Rancher RKE2 1.22 (v1.22)                                                                                                                                                                                                                                     13 kB/s | 2.9 kB     00:00    
No match for argument: rke2-server-1.22.15~rke2r1
Error: Unable to find a match: rke2-server-1.22.15~rke2r1

gray-lawyer-73831

09/27/2022, 4:38 PM

For the individual version channels, it pulls from stable. See this line in the output:

[INFO]  using 1.22 series from channel stable

. As these releases just came out, they aren’t in stable yet. They’ll probably be there tomorrow though as generally we push them to stable approx. 24 hours after release as long as there are no glaring issues found from the early users in that time. So, to answer your question:

What’s the best way to identify the latest stable patch version of a minor version?

Do what you’re doing, but remove the explicit “INSTALL_RKE2_VERSION” bit. If you explicitly want that version before it’s available in our stable channels, just update the channel to

latest

👍

shy-zebra-53074

09/27/2022, 4:39 PM

perfect ty!

🚀 1

5 Views

#rke2 Join Slack