rancher-desktop icon indicating copy to clipboard operation
rancher-desktop copied to clipboard

Rancher 2.x fails to start on some Linux machines

Open adamkpickering opened this issue 2 years ago • 2 comments

Actual Behavior

Test case 7 on the test plan states the following:

nerdctl run --privileged -d --restart=no -p 8080:80 -p 8443:443 rancher/rancher

Note: Sometimes it takes a few sec till you can see the page at https://localhost:8443/ after the nerdctl run .. command is run. If you see Page cannot be displayed in browser, please wait for few sec and try again.

While doing testing it was found that Rancher 2.x could not be installed in this manner. It just ran for a long time and never started. I tried increasing the number of processors available to each VM from 2 to 4 and it still failed. Each machine was allocated 8GB of memory. I did look at the logs, and I remember that it appeared that something different was failing each time. Unfortunately I did not keep any of them. However I should be able to reproduce the issue if needed.

Steps to Reproduce

Follow test case 7 on the test plan.

Result

Rancher never comes up - it just times out.

Expected Behavior

I expected Rancher to come up without issue.

Additional Information

This issue occurred in three different VMs running:

  • Rocky 8
  • Fedora 35
  • Ubuntu 22.04

RD was installed via AppImage on Fedora and Rocky. It was installed via deb on Ubuntu.

Everyone but me got it working fine. So it may be something with my environment?

Rancher Desktop Version

1.2.0-587-g33cf71b5

Rancher Desktop K8s Version

Unknown

Which container runtime are you using?

containerd (nerdctl)

What operating system are you using?

Other Linux

Operating System / Build Version

See "Additional Information"

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

No response

Windows User Only

No response

adamkpickering avatar May 06 '22 20:05 adamkpickering

Failing for 1.4 prelease testing on Fedora 35 and 36. Logs are attached. fedora_35_nerdctl_smoke_test_logs.txt fedora_36_nerdctl_smoke_test_logs.txt .

adamkpickering avatar May 26 '22 17:05 adamkpickering

Just tested this again - it is still failing on Fedora 35 and 36 when testing with the 1.5.1 AppImage.

adamkpickering avatar Aug 23 '22 21:08 adamkpickering

Tested again. Still failing for 1.9.0 RC1 testing on both Fedora 37 and 38.

adamkpickering avatar Jun 08 '23 22:06 adamkpickering