-
Notifications
You must be signed in to change notification settings - Fork 8
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
feat: k3d Rancher Desktop #342
Conversation
If you're new to commit signing, there are different ways to set it up: Sign commits with
|
@claywd: can you sign the commits please, and I'll review it after. |
cfb4631
to
8e0ac57
Compare
If you're new to commit signing, there are different ways to set it up: Sign commits with
|
1 similar comment
If you're new to commit signing, there are different ways to set it up: Sign commits with
|
f741ff6
to
b508f36
Compare
If you're new to commit signing, there are different ways to set it up: Sign commits with
|
b508f36
to
78bc126
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@claywd : in the WSL section, you wrote "There are limitations within Docker Desktop and how it manages volumes which prevent us from supporting it at this moment.", but AFAIK, kubefirst with WSL is working? This part is not clear to me.
That was my bad. I meant rancher-desktop |
Signed-off-by: Clayton Dittman <[email protected]>
Updates docs on k3d local and https flow.