[wp-trac] [WordPress Trac] #62196: Improve documentation for using the local Docker environment on Windows

[WordPress Trac]

#62196: Improve documentation for using the local Docker environment on Windows
----------------------------------------+-----------------------------
 Reporter:  desrosj                     |       Owner:  (none)
     Type:  defect (bug)                |      Status:  new
 Priority:  normal                      |   Milestone:  Future Release
Component:  Build/Test Tools            |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  needs-patch good-first-bug  |     Focuses:
----------------------------------------+-----------------------------

Comment (by SirLouen):

 Replying to [comment:3 karthikeya01]:
 > I think for latest Windows versions Docker uses WSL backend by default
 to setup.

 I can confirm as @karthikeya01 said that there are no issues with the
 basic setup both in Windows PowerShell and inside the WSL (Ubuntu in my
 case) shell.

 Once I tried running over Hyper-V with VMWare and was a little tricky
 because you have to configure docker connection to access "remotely" to
 the VM, its well handled by docker desktop.

 For nested virtualization, I have no idea on how it runs, but also seems
 to be possible: https://docs.docker.com/desktop/setup/vm-vdi/

 Mainly I believe that instead of adding "installation notes" for each
 system, I think its OK as it's currently explained:

 > You will also need Docker installed and running on your computer. Docker
 is the virtualization software that powers the local development
 environment. Docker can be installed just like any other regular
 application.

 As long as you can run `docker` in whatever shell you use, you have your
 `npm` set-up, no extra instructions are needed. Docker Desktop can be
 mentioned.

 Instead of using `choco` I think the more modern aproach could be also
 commented with `winget`

 {{{
 winget install -e --id Docker.DockerDesktop
 }}}

 And for NPM, winget also installing `fnm`: https://nodejs.org/en/download/
 (reminding to use a lesser version of NPM).

 Finally, the only trouble is the file permissions part. Maybe some
 information could be expanded on this topic. By default, you will not be
 able to play around with files and folders within the working WP
 installation, not even with `fs_method` `direct` (it will trigger the
 Connection Information). This is mainly why I work directly on the WSL2
 container and not over my Windows Filesystem (for Windows testing I prefer
 to use FlyEnv).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62196#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform