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

After restart rancher desktop, the local-path-config will be restored #6917

Closed
flyeric0212 opened this issue May 17, 2024 · 1 comment
Closed
Assignees
Labels
kind/bug Something isn't working
Milestone

Comments

@flyeric0212
Copy link

Actual Behavior

After restart rancher desktop, the local-path-config will be restored

Steps to Reproduce

image

I changed the paths field。

Result

After restart rancher desktop, the local-path-config will be restored.
image

Expected Behavior

Do not be restored.

Additional Information

No response

Rancher Desktop Version

1.12.3

Rancher Desktop K8s Version

1.26.5

Which container engine are you using?

moby (docker cli)

What operating system are you using?

macOS

Operating System / Build Version

Sonoma 14.5

What CPU architecture are you using?

x64

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

None

Windows User Only

No response

@flyeric0212 flyeric0212 added the kind/bug Something isn't working label May 17, 2024
@gunamata gunamata added this to the 1.15 milestone May 17, 2024
@gunamata gunamata modified the milestones: 1.15, 1.16 Jul 24, 2024
@jandubois jandubois modified the milestones: 1.16, 1.17 Aug 30, 2024
@jandubois
Copy link
Member

After restart rancher desktop, the local-path-config will be restored.

This happens because k3s will re-apply the local-storage.yaml manifest on each restart, removing your settings. And you can't edit the manifest either (I tried), as it gets re-extracted from the bundled manifests each time.

The best workaround is to tell k3s to stop applying the manifest:

$ rdctl shell sudo touch /var/lib/rancher/k3s/server/manifests/local-storage.yaml.skip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants