You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a SUSE Linux user, I want a reasonable and safe installation of rancher desktop from IDEasy so that I can feel safe.
However, I see this:
We need to run the following privileged command(s):
sudo zypper addrepo https://download.opensuse.org/repositories/isv:/Rancher:/stable/rpm/isv:Rancher:stable.repo",
sudo zypper --no-gpg-checks install rancher-desktop=1.17.0*
This will require root permissions!
[sudo] password for root:
When I saw --no-gpg-checks I cancelled the request since I did trust this approach and want to stay in control.
BTW: What is the reason for the asterisk after the version (so why is it 1.17.0* instead of just 1.17.0)? Maybe there is a good reason since maybe Linux distributions may add additional packaging revisions to the version number if they did some improvement without changing the version and source-code (of rancher desktop in this case)... I am just curios as this is just done this way for SUSE in our code and I have no clue why.
The text was updated successfully, but these errors were encountered:
As a SUSE Linux user, I want a reasonable and safe installation of rancher desktop from IDEasy so that I can feel safe.
However, I see this:
When I saw
--no-gpg-checks
I cancelled the request since I did trust this approach and want to stay in control.Please consider removing
--no-gpg-checks
and allow the user to decide interactively if he wants to reject, trust once or trust permanent to the certificate.https://github.com/devonfw/IDEasy/blob/9b3431944065975fdccf29071f359478690eeeb5/cli/src/main/java/com/devonfw/tools/ide/tool/docker/Docker.java#L65C36-L65C51
BTW: What is the reason for the asterisk after the version (so why is it
1.17.0*
instead of just1.17.0
)? Maybe there is a good reason since maybe Linux distributions may add additional packaging revisions to the version number if they did some improvement without changing the version and source-code (of rancher desktop in this case)... I am just curios as this is just done this way for SUSE in our code and I have no clue why.The text was updated successfully, but these errors were encountered: