Target rustup-init.exe to run on Microsoft Nano Server

[cdhunt]

Describe the problem you are trying to solve

I'm trying to build a Windows-based build container for Rust-lang. Initially, I tried to run rustup-init.exe in a Nano Server 1903 container and the process immediately dies. The verbose flag doesn't provide any extra information. The exit code is -1073741515.

This works fine in a Windows Server Core 1903 container, but the Nano image is 400MB and the Server Core image is 5GB.

Describe the solution you'd like

Being able to run the Rust toolchain in a Nano container would help in development in testing.

Notes

docker run --rm -it mcr.microsoft.com/powershell:nanoserver-1903
> iwr https://win.rustup.rs/ -outfile rustup-init.exe
> .\rustup-init.exe -y -v --default-toolchain nightly-2019-09-11

[kinnison]

At a guess, nano might be lacking the VC++ redist stuff though I appreciate I'm not a Windows person so can't be certain.

[cdhunt]

I copied in vcruntime140.dll and msvcp140.dll into the image and still no go. I'm also just throwing stuff against the wall to see if it sticks.

[mati865]

https://win.rustup.rs/ points to 32 bit executable but Nano can only run 64 bit binaries.
You can try using this: https://win.rustup.rs/x86_64

[cdhunt]

That executable does produce different results.

warning: installing msvc toolchain without its prerequisites
error: permission denied
info: caused by: The system cannot find the file specified. (os error 2)

[mati865]

I don't know how rustup Windows code works so I cannot help further but at least it got to the part where rustup is executed.

[cdhunt]

I recall someone working on a PowerShell version of rustup-init, but can't find it now.

[kinnison]

The incomplete rustup-init.ps1 work is in #1878

[cdhunt]

Thanks, @kinnison. I even commented on that. Not sure why I couldn't find it. I'll take a look at that again.

[kinnison]

@cdhunt Did you get any further with this?

[cdhunt]

Not really. I tried a number of methods for installing VS Build Tools. I couldn't find a package that would install link.exe and couldn't find a reliable hosted copy of the binary to manually add it.

[kinnison]

Oh dear. I wonder who might be able to assist. I have basically zero Windows knowledge :(

[cdhunt]

@jonathandturner working on https://github.com/nushell/nushell is probably a good contact. I don't know much about C build tools on Windows either.

[ljani]

Now even mcr.microsoft.com/windows/servercore:1909 seems to have problems running rustup-init.exe. docker build just hangs in the RUN command:

> docker build -t mytest .
Sending build context to Docker daemon  142.8kB
Step 1/4 : FROM mcr.microsoft.com/windows/servercore:1909
 ---> ec69effa48a7
Step 2/4 : RUN curl --output rustup-init.exe --show-error --silent --location "https://win.rustup.rs/x86_64" && rustup-init.exe -y --profile default --default-toolchain nightly && echo test
 ---> Running in 14a3b34da3f4
warning: installing msvc toolchain without its prerequisites
info: profile set to 'default'
info: syncing channel updates for 'nightly-x86_64-pc-windows-msvc'
info: latest update on 2019-11-15, rust version 1.41.0-nightly (82cf3a448 2019-11-14)
warning: Force-skipping unavailable component 'clippy-x86_64-pc-windows-msvc'
info: downloading component 'cargo'
info: downloading component 'rust-docs'
info: downloading component 'rust-std'
info: downloading component 'rustc'
info: downloading component 'rustc-dev'
info: downloading component 'rustfmt'
info: installing component 'cargo'
info: installing component 'rust-docs'
info: installing component 'rust-std'
info: installing component 'rustc'
info: installing component 'rustc-dev'
info: installing component 'rustfmt'
info: default toolchain set to 'nightly'

  nightly installed - rustc 1.41.0-nightly (82cf3a448 2019-11-14)


Rust is installed now. Great!

To get started you need Cargo's bin directory (%USERPROFILE%.cargo\bin) in your
PATH
environment variable. Future applications will automatically have the
correct environment, but you may need to restart your current shell.
test
...Hung...

[kinnison]

The default profile includes rust-docs which is never fast on Windows -- you might find it's sat there dealing with the roughly twenty-thousand files for that. Otherwise I'm not sure -- can you get procmon or some other tracing tool onto the docker to see what it's up to?