Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rancher Desktop fails to apply settings when 9p mount type is selected #5865

Closed
adamkpickering opened this issue Oct 30, 2023 · 3 comments
Closed
Labels
area/volume Access to host volumes from inside the VM or containers kind/bug Something isn't working platform/linux

Comments

@adamkpickering
Copy link
Member

Actual Behavior

The backend fails to restart when the 9p mount type is selected and Apply is clicked.

Steps to Reproduce

  1. Set Preferences > Virtual Machine > Volumes > Mount Type to 9p
  2. Leave the other settings, such as Cache Mode and Protocol Version, set to their defaults.
  3. Click apply.

Result

An error dialog pops up.

Expected Behavior

Rancher Desktop should restart the backend successfully.

Additional Information

I first noticed this when testing 1.11 RC1. However, it happens in the exact same way on 1.10.0.

logs.zip

Rancher Desktop Version

1.10.0

Rancher Desktop K8s Version

1.27.6

Which container engine are you using?

containerd (nerdctl)

What operating system are you using?

Other Linux

Operating System / Build Version

Fedora 38 GNOME

What CPU architecture are you using?

x64

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

AppImage

Windows User Only

No response

@adamkpickering adamkpickering added the kind/bug Something isn't working label Oct 30, 2023
@jandubois jandubois added platform/linux area/volume Access to host volumes from inside the VM or containers labels Oct 30, 2023
@jandubois
Copy link
Member

An error dialog pops up.

Could you attach a screenshot of the dialog when this happens?

@jandubois
Copy link
Member

Also please make sure symlinked files are included properly in the logs.zip. They are just stored as symlinks without their targets.

@adamkpickering
Copy link
Member Author

Closing as this is a duplicate of #4943.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/volume Access to host volumes from inside the VM or containers kind/bug Something isn't working platform/linux
Projects
None yet
Development

No branches or pull requests

2 participants