CI for Windows Server 2016 Version 1709

dotnet / dotnet-docker-nightly

This repository has moved to the nightly branch of dotnet/dotnet-docker.

https://github.com/dotnet/dotnet-docker/tree/nightly

MIT License

35 stars 30 forks source link

CI for Windows Server 2016 Version 1709 #481

Closed ravimeda closed 6 years ago

ravimeda commented 6 years ago

Windows Server 2016 Version 1709 is a prerequisite for building RS3 based images. Helix provides a queue, windows.10.amd64.serverrs3.open, for 1709. This queue can also be used to process CI jobs. Thus, unblocking https://github.com/dotnet/dotnet-docker-nightly/issues/468.

ravimeda commented 6 years ago

@dotnet-bot test ci please

ravimeda commented 6 years ago

@dotnet-bot test ci please

ravimeda commented 6 years ago

@dotnet-bot test ci please

ravimeda commented 6 years ago

@dotnet-bot test ci please

ravimeda commented 6 years ago

@dotnet-bot test ci please

ravimeda commented 6 years ago

@dotnet-bot test ci please

ravimeda commented 6 years ago

@dotnet-bot test ci please

ravimeda commented 6 years ago

@dotnet-bot test this please

ravimeda commented 6 years ago

@dotnet-bot test ci please

ravimeda commented 6 years ago

@dotnet-bot test ci please

ravimeda commented 6 years ago

Status update - to run dotnet/docker tests in a Nano Server 1709 VM, some interesting changes are required.

Default user in a container running Nano Server 1709 is ContainerUser. This user will not have access to files on a volume. Only the ContainerAdministrator has access to those files. Refer to https://github.com/dotnet/dotnet-docker-nightly/pull/506
Since ContainerUser does not have admin level access, in a Nano Server 1709 Dockerfile, to perform an action that requires admin access such as setting a system environment variable, user should be switch to ContainerAdministrator. Refer to https://github.com/dotnet/dotnet-docker-nightly/pull/505

A Nano Server 1709 VM in now available in CI.

MichaelSimons commented 6 years ago

@ravimeda, I merged your two PR's. I think you can pull master into your branch, verify CI is working, and then this PR should be merged.

ravimeda commented 6 years ago

@dotnet-bot test ci please

ravimeda commented 6 years ago

@dotnet-bot test ci please

ravimeda commented 6 years ago

@dotnet-bot test ci please

ravimeda commented 6 years ago

@dotnet-bot test ci please

ravimeda commented 6 years ago

@dotnet-bot test ci please

ravimeda commented 6 years ago

@dotnet-bot test ci please