blog: update old blog post to not user "none driver" for minikube

[medyagh]

minikube has added docker driver since 2019 and "none driver" is not recommended and only meant to be used by CI or when there is no other option. which causes issues like this for users kubernetes/minikube#8568 (comment)

we strongly suggest using other drivers. if u dont specify the --driver flag, minikube will choose the best driver for your environment.

I suggest updating this blog post to use minikube with either docker driver (or not set the --driver at all) to let minikube choose the best driver:

blog post: https://kubernetes.io/blog/2020/05/21/wsl-docker-kubernetes-on-the-windows-desktop/#minikube-updating-the-host

@idvoretskyi

[idvoretskyi]

/assign

@medyagh thanks for catching this!

[idvoretskyi]

/assign @nunix

[k8s-ci-robot]

@idvoretskyi: GitHub didn't allow me to assign the following users: nunix.

Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @nunix

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[nunix]

first, thanks a lot for your feedback @medyagh , really appreciated.

Concerning the driver, I think the timing is very good as WSL2 is now "live", so the Windows Insiders is no more needed and the default kernel used is the 5.4.x and is built with modules needed by Kubernetes and/or Docker.

I will go through the blog post and refresh it entirely, so we keep only one blog post, but this will could be seen as a V2

[idvoretskyi]

/assign @nunix

[sftim]

/sig windows
I think

@nunix we usually don't make substantial revisions to published blog articles. If you are planning a big revision, it might be better to propose a new article and then update the old article to start with a notice about reading the new article instead.
/area blog
/language en

[nunix]

thanks a lot @sftim, I was actually start thinking the same ... but I might then just remove the part of the none driver to address this issue and then concentrate on a new blog (might take more time due to my workload lately)

[celestehorgan]

/triage accepted

[medyagh]

@nunix I wonder was there a PR that made for this issue, is this still being worked on ?

[nunix]

hi @medyagh , sorry I have some delay here. I need to test the docker provider again, my first test didn't work, but I guess I did something wrong. I will amend the blog post asap.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[BioGeek]

/remove-lifecycle stale

@nunix Can you comment if this is something you're still working on?

@sharifelgamal mentioned in issue kubernetes/minikube#10343 that proper support for WSL with the docker and none drivers is on the roadmap for this year, so maybe you're waiting on that?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.