Dead link https://www.docker.com/products/docker-toolbox

[gunnarx]

This redirects to the home page of "get docker": https://www.docker.com/products/docker-toolbox, so it's 404 I guess. AFAICT this is an appropriate replacement: https://www.docker.com/docker-windows

I would send a PR but I didn't see right away out how to do that for the Wiki text (where's the markdown source?)

EDIT: Oh... this workaround for Wiki PRs shows how to get the .md but still a painful workaround for the PR.

[gunnarx]

Or if you're committed to toolbox, maybe this:
https://docs.docker.com/toolbox/toolbox_install_windows
(toolbox is stated to be a legacy method, but the newest methods depends on Hyper-V and such, so what do I know. Not a Windows expert here, I just came across this)

Related issue: #3

[rewitt1]

Hi,

The reason I haven't set up something for the wiki to have PR as in the link you posted, is because as you can see, the wiki hasn't changed much.

However, I like the idea for crediting people for pointing things out, and so even though I just updated the wiki, the question is still what is the best way to give you credit? Is this issue enough, or do you have another idea? If you see an issue with the wiki now that I updated it let me know.

And it's not that we're committed to toolbox, so much as Hyper-V is not supported on Windows 10 Home, only on the Pro and higher versions. So when I originally wrote the docs, I opted for the solution that works regardless of the Windows version.

I probably should try to set up something such as the workaround for PRs that you posted, so that people can try to contribute to the docs more easily, and considering I only work on the project in my free time now.

Thanks!

[gunnarx]

The issue is enough - just fix and close. This was a drive-by thing, cause I hardly ever use Windows and have no plans to use Docker on Windows. It's a really odd combination, but I can see how Windows users still can get some benefit from it. Mostly I appreciate the activities in the Yocto project to improve on the experience using crops & Docker.