user2151: I am trying to run the Plutus playground using the Gitbook recipe (https://docs.plutus-community.com/docs/setup/WindowsWSL.html).
At step 15, the server starts fine, but trying to run the client with "npm run start" fails with the following
    [info] Copying from global cache: "tuples"
    [info] Copying from global cache: "web-html"
    [error] Installation failed
    [error] Error:
    [error] .spago/__download-catenable-lists-v5.0.1-1293619144260987/download: rename: permission denied (Permission denied)
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! plutus-playground-client@1.0.0 purs:compile: `spago build`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the plutus-playground-client@1.0.0 purs:compile script.

It seems that the npm script is trying to download something into a (read-only) nix store. How do I get the client to start?
I found some other issues (e.g. Installation failed on Ubuntu 20.04 in WSL on Windows 10 #689) reporting this error, but the reported fix is to close VSCode, so it is no longer accessing the build directories.  I am not currently using VSCode.  However, to make sure it was not some other lingering file contention, I restarted my PC and did nothing except the build on a newly restarted system.  Same error.

user2151: I found a resolution to the problem.
In sheer frustration, I spun up a Windows Hyper-Visor VM and started provisioning it from scratch with WSL2, Nix, etc, and nothing else.  After cloning the plutus repository, I got a strange git error (https://github.com/docker/for-win/issues/6284).  The resolution was to move the git repository from the windows-hosted file system (e.g. C:...) to the Ubuntu-hosted file system (\WSL$/mnt...).  Even though the systems are allegedly interoperable, apparently it is not perfect.
Re-cloning the plutus repository under my linux home directory caused the build problem to disappear.   (I had been downloading under my Windows-home directory when the error occured.)
Now I can do my Plutus Pioneer homework...

2151: <p>I am trying to run the Plutus playground using the Gitbook recipe (<a href="https://docs.plutus-community.com/docs/setup/WindowsWSL.html" rel="nofollow noreferrer">https://docs.plutus-community.com/docs/setup/WindowsWSL.html</a>).
At step 15, the server starts fine, but trying to run the client with &quot;npm run start&quot; fails with the following</p>
<pre><code>    [info] Copying from global cache: &quot;tuples&quot;
    [info] Copying from global cache: &quot;web-html&quot;
    [error] Installation failed
    [error] Error:
    [error] .spago/__download-catenable-lists-v5.0.1-1293619144260987/download: rename: permission denied (Permission denied)
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! plutus-playground-client@1.0.0 purs:compile: `spago build`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the plutus-playground-client@1.0.0 purs:compile script.
</code></pre>
<p>It seems that the npm script is trying to download something into a (read-only) nix store. How do I get the client to start?</p>
<p>I found some other issues (e.g. <a href="https://github.com/purescript/spago/issues/689" rel="nofollow noreferrer">Installation failed on Ubuntu 20.04 in WSL on Windows 10 #689</a>) reporting this error, but the reported fix is to close VSCode, so it is no longer accessing the build directories.  I am not currently using VSCode.  However, to make sure it was not some other lingering file contention, I restarted my PC and did nothing except the build on a newly restarted system.  Same error.</p>
 2151: <p>I found a resolution to the problem.</p>
<p>In sheer frustration, I spun up a Windows Hyper-Visor VM and started provisioning it from scratch with WSL2, Nix, etc, and nothing else.  After cloning the plutus repository, I got a strange git error (<a href="https://github.com/docker/for-win/issues/6284" rel="nofollow noreferrer">https://github.com/docker/for-win/issues/6284</a>).  The resolution was to move the git repository from the windows-hosted file system (e.g. C:...) to the Ubuntu-hosted file system (\WSL$/mnt...).  Even though the systems are allegedly interoperable, apparently it is not perfect.</p>
<p>Re-cloning the plutus repository under my linux home directory caused the build problem to disappear.   (I had been downloading under my Windows-home directory when the error occured.)</p>
<p>Now I can do my Plutus Pioneer homework...</p>
