Repository navigation
Building LTS v12.x on Windows Fails The system cannot find the file specified." #32044
Description
- Version: 12.x
- Platform: Windows
- Subsystem:
I took the documentation specified in Building.md and converted that into a DockerFile. I had to make some additions to supplement the boxstarter scripts because that ran into errors installing the build tools. To get around that issue I installed those first via npm, following guidelines in this post, then called the boxstarter scripts. This enabled me to get passed that particular problem but now I have a new issue which is detailed below in the console output. I have included a dockerfile to reproduce the issue. Any assistance will be greatly appreciated.
Output of the build
C:\node>.\vcbuild full-icu download-all
Looking for Python
Python 2 found in C:\Python27\\python.exe
Looking for NASM
Looking for Visual Studio 2017
Found MSVS version 15.0
configure "--download=all" --with-intl=full-icu --dest-cpu=x64
INFO: Using floating patch "tools/icu/patches/64/source/common/putil.cpp" from "tools/icu"
INFO: Using floating patch "tools/icu/patches/64/source/i18n/dtptngen.cpp" from "tools/icu"
Warning: Missing input files:
tools\msvs\genfiles\node_etw_provider.rc
tools\msvs\genfiles\node_etw_provider.h
tools\v8_gypfiles\..\..\deps\v8\src\regexp\regexp-special-case.h
INFO: configure completed successfully
Project files generated.
The system cannot find the file specified.Dockerfile to reproduce the behaviour
ARG version=ltsc2019
FROM mcr.microsoft.com/windows/servercore:$version
ENV chocolateyUseWindowsCompression false
RUN powershell -Command \
iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1')); \
choco feature disable --name showDownloadProgress
RUN powershell choco install nodejs-lts -y
RUN npm install --global --production windows-build-tools
RUN npm config set msvs_version 2017 -global
RUN npm install --global node-gyp --no-optional
RUN powershell choco install vim -y
RUN powershell -Command \
iex ((New-Object System.Net.WebClient).DownloadString('https://boxstarter.org/bootstrapper.ps1')) ; \
Get-Boxstarter -Force ; \
Install-BoxstarterPackage https://raw.githubusercontent.com/nodejs/node/master/tools/bootstrap/windows_boxstarter -DisableReboots
RUN powershell git clone https://github.com/nodejs/node.git
RUN powershell Set-Location -Path C:\Node; git checkout v12.x
RUN powershell Set-Location -Path C:\Node; .\vcbuild full-icu download-all
Activity
bzoz commentedon Mar 3, 2020
Building v12 works fine on my local machine.
@jwyglendowski-precisionlender , you say that the Boxstarter script run into some issues. What were those issues exactly?
If for whatever reason installing VS does not work through the Boxstarter but works using npm, there is no need to run the Boxstarter script. You are only missing NASM and git. With:
you should be able to build Node.
Finally, remove
The
node-gypbundled with Node should work.If you still are having issues, set
DEBUG_HELPERenvironment variable to 1 before running thevcbuildscript. It will produce a lot more output.jwyglendowski-precisionlender commentedon Mar 3, 2020
@bzoz Thanks for replying.
Here is the error console log for the boxstarter failure for reference. I will adjustment my DockerFile removing out the boxster bits for the two choco commands. Will run the new docker build which should fail running the node build based on previous runs. That being said I will add the
DEBUG_HELPERas you have suggested and report back my findings.jwyglendowski-precisionlender commentedon Mar 3, 2020
@bzoz I have the full log but I will include just the last bits.
bzoz commentedon Mar 11, 2020
@jwyglendowski-precisionlender could you try the build again?
I also saw this
CERTIFICATE_VERIFY_FAILED, but when I sat down today to investigate it, it no longer reproduces. Could you give it another try?jwyglendowski-precisionlender commentedon Mar 11, 2020
@bzoz I am still getting the error. I run the following docker build file and command. Are you running this in Docker during your test?
Docker Build:
docker build -t nodejs/12.x:latest --no-cache .My docker file is the following:
Still getting
bzoz commentedon Mar 11, 2020
I'm running this from a Windows VM and I saw the cert error last week. It worked today when I tried this on a clean machine, although I skipped
RUN npm install --global node-gyp --no-optionalsince installing node-gyp usually messes things up.I'll give it a spin in a docker container.
bzoz commentedon Mar 12, 2020
@jwyglendowski-precisionlender: ok, it reproduces almost 100% of times. The download stage did work once when I tried it in an interactive terminal though.
As a temporary workaround:
@nodejs/docker @nodejs/build @nodejs/platform-windows - for whatever reason building v12.x with full-icu in a Docker container fails when trying to download the ICU files:
This does not happen on master since full ICU is now included by default (#29522). Any ideas?
jwyglendowski-precisionlender commentedon Mar 12, 2020
@bzoz Thanks. I am running that now and as soon as it's complete I will post the results.
jwyglendowski-precisionlender commentedon Mar 12, 2020
@bzoz I made a minor change to the Dockerfile so that it would download the ICU from the script
So the build version
Is there an easy way to build it without the -pre in the version? Is there an ENV variable I can set? Is there an easy way to know which version of FULL-ICU goes with 12.x LTS?
sam-github commentedon Mar 12, 2020
Build from a tag,
v12.16.1(for example), if it says v12.16.2-pre, that's what it is, the 12.x dev branch.jwyglendowski-precisionlender commentedon Mar 13, 2020
@sam-github Thanks Sam. That did do the trick on the node side. Do you know of a way to determine which ICU version goes with a particular node version since the
vcbuild full-icu download-alldoesn't work?bzoz commentedon Mar 13, 2020
@jwyglendowski-precisionlender it is in tools/icu/current_ver.dep file.
jwyglendowski-precisionlender commentedon Mar 13, 2020
@bzoz Cool. So I should be able to create a complete docker file where all I have to specify is a tag version then everything else should theoretically take care of itself. Have you looked into dev containers. It might be useful for others or just have a dockerfile for each platform. Even if you don't this thread will provide documentation on how to do it. Once I have a completed dockerfile that pulls the url from the
tools/icu/current_ver.depfile I will post it here.jwyglendowski-precisionlender commentedon Mar 13, 2020
@bzoz Here is the updated Dockerfile that will pull the latest full icu based on the tools folder. I may refine a bit more but it's functional.
sam-github commentedon Mar 13, 2020
I'm not sure how much time you want to sink into this, but perhaps its worth joining or working with the github.com/nodejs/docker team (@nodejs/docker ) to start producing windows docker images? I don't know if they have the expertise and time to do it themselves, maybe they do, but I'd imagine they'd be happy to have new members to add this kind of support.
jwyglendowski-precisionlender commentedon Mar 16, 2020
@sam-github Thanks for the suggestion. I will keep it under consideration.
bzoz commentedon May 19, 2020
Adding
disables this verification thingy, and the Node builds.
Complete Dockerfile:
bzoz commentedon May 21, 2020
I'm going to close this, since we have a workaround and this is more an issue with Python/Docker and not with Node. Feel free to reopen if you have further issues.