issue
Use windows nodejs image (server core in 1803/1809) to build html source code in a mount volume(docker volume, host-volume and G driver solution), all build in mount volume are failure when in lerna bootstrap with the same kind of Error "Error: EPERM: operation not permitted, symlink".
Expected behavior
Use windows nodejs image to build source code in a mount volume, npm install successfully
Actual behavior
npm WARN uid-web@1.1.0 requires a peer of zone.js@^0.8.29 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@0.3.8 (node_modules\json-sass\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@0.3.8: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
lerna@2.11.0
added 2008 packages from 1982 contributors in 166.342s
npm timing npm Completed in 166795ms
npm info ok
"Deleting current lerna json file"
"Copying lerna-bootstrap.json to current folder"
1 file(s) copied.
"rename lerna-bootstrap.json to lerna.json"
lerna info version 2.11.0
lerna info versioning independent
lerna info scope @wuitk6/*
lerna info Bootstrapping 7 packages
lerna info lifecycle preinstall
lerna WARN EHOIST_ROOT_VERSION The repository root depends on @types/d3@^3.5.41, which differs from the more common @types/d3@^3.5.38.
lerna WARN EHOIST_PKG_VERSION "@wuitk6/examples" package depends on @types/d3@^3.5.38, which differs from the hoisted @types/d3@^3.5.41.
lerna WARN EHOIST_PKG_VERSION "@wuitk6/gallery" package depends on @types/d3@^3.5.38, which differs from the hoisted @types/d3@^3.5.41.
lerna info Installing external dependencies
lerna info hoist Installing hoisted dependencies into root
lerna info hoist Pruning hoisted dependencies
lerna info hoist Finished pruning hoisted dependencies
lerna info hoist Finished installing in root
lerna info Symlinking packages and binaries
lerna ERR! execute callback with error
lerna ERR!
{ [Error: EPERM: operation not permitted, symlink 'C:\data\uid-web\packages\core' -> 'C:\data\uid-web\packages\angular\node_modules\@wuitk6\core']
errno: -4048,
code: 'EPERM',
syscall: 'symlink',
path: 'C:\data\uid-web\packages\core',
dest:
'C:\data\uid-web\packages\angular\node_modules\@wuitk6\core',
exitCode: 1 }
error in lerna bootstrap
Environment Information
Windows Version: windows 10 1809
Docker Desktop Version: 19.03.2
issue Use windows nodejs image (server core in 1803/1809) to build html source code in a mount volume(docker volume, host-volume and G driver solution), all build in mount volume are failure when in lerna bootstrap with the same kind of Error "Error: EPERM: operation not permitted, symlink".
Expected behavior Use windows nodejs image to build source code in a mount volume, npm install successfully
Actual behavior npm WARN uid-web@1.1.0 requires a peer of zone.js@^0.8.29 but none is installed. You must install peer dependencies yourself. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@0.3.8 (node_modules\json-sass\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@0.3.8: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
Environment Information Windows Version: windows 10 1809 Docker Desktop Version: 19.03.2
docker file you can find docker file from https://raw.githubusercontent.com/StefanScherer/dockerfiles-windows/master/node/10/Dockerfile, only add below 2 line for your G drive solution
VOLUME C:\data RUN Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\DOS Devices' -Name 'G:' -Value "\??\C:\data" -Type String;
Steps to reproduce the behavior