Closed matthargett closed 7 years ago
Please look at this thread for Windows Server 2016 status: http://help.appveyor.com/discussions/questions/2652-windows-server-2016
@FeodorFitsner any updates on this? is there a way my account can be added to the beta list, like you did with VS2017 RC?
Still working on that. Struggling to install Docker on Windows Server 2016 image provided by Google Compute Cloud.
Tweeted to @csells asking for some assistance. Hopefully he can help get some attention to the issue on the Google side.
Thanks!
What's the problem with Docker on GCP Windows Server 2016?
Hi Chris,
thanks for looking into that!
What I'm really trying to do is simply:
Do you have any success deploying Docker to Windows Server 2016 machine hosted on GCE?
Hi Feodor,
This was a feature incompatibility between GCE virtual network and Docker. We are working on a fix at the moment. The work around right now is to turn off Rsc feature before installing docker.
PS C:> netsh netkvm setparam 0 *RscIPv4 0 PS C:> netsh netkvm restart 0
Please refer to the documentation below for full detail.
https://cloud.google.com/compute/docs/containers/#docker_on_windows
It worked like a charm, yay! 😄 Thank you guys for the help with solving that - we are unblocked now!
Awesome! Let me know when we can try it so we can finally run our Universal Windows Tests in AppVeyor!
PS: we've been emailing team@appveyor.com to try and set up a call to discuss enterprise business plans, but haven't been getting a response there. Emails would have been from bluejeans.com or bluejeansnet.com
Oh, will reply on those messages today, sorry for the delay.
Hi there, on the topic of windows server 2016 for appveyor. When executing Powershell install-module is questioning credentials installing PScribo. I have asked the PScribo author and he found that the environment for virtual machine aren't updated to the latest. iainbrighton/PScribo#30 Can I ask if Window Server 2016 is scheduled soon or is there a workaround on Powershell side on appveyor virtual machine. Thanks, Peter.
We'll start offering Windows Server 2016
image in a day-two. Stay tuned!
Windows Server 2016
image is ready. Please let us know if you want to give it a try!
We would like to try it (for the KivyOrg account), and I guess on my personal account as well. Thanks!
I'd definitely check it out as I'd like to verify some Chocolatey packages work across all the versions of server available.
please add @bluejeans @rozele and @matthargett so we can test UWP build of React Native Windows
Please add @nibanks (nibanks/openthread) and @jwhui (jwhui/openthread) so we can test Windows 10 driver development.
@dragon788, @bluejeans, @rozele, @matthargett, @nibanks, @jwhui added.
@matham added to "KivyOrg".
@FeodorFitsner Thanks for the add.
So a few comments (should I do this here or on the message boards?), after adding os: Windows Server 2016
the startup was quite slow; it took a few minutes to get started and then the cloning seemed slow. However, the bigger issue is that it still seems to have only opengl 1.1 installed. That's the main reason for us to want to use it.
We do have install: - ps: iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/appveyor/ci/master/scripts/enable-desktop.ps1'))
to enable the desktop, is there maybe something else we need to do?
@FeodorFitsner I validated that I can successfully build, install and run Windows 10 drivers on the image you provided. Thanks!
I also noted that the build seemed to take a lot longer than usual to get started. Is this expected?
My build finally finished and it essentially doubled in the time it took to build, as you can see from my history, from ~23 minutes to ~47 minutes.
@nibanks Thanks for the feedback! That's right - Windows Server 2016
image builds run on GCE and it takes around 3-4 minutes to provision and boot a new build worker VM there. As your build has multiple jobs those 3-4 additional minutes before each job add to the overall build time.
@matham re: opengl - there is a "stock" Windows Server 2016 with VS 2015 on top of it. What would you need to do to get a different version of OpenGL?
@FeodorFitsner hmm, I may have misunderstood what Server 2016 adds. I thought you'd have opengl support just with the vm, but it may need an actual graphics card that supports opengl > 1.1. See the section under 1. OpenGL 4.4 and OpenCL 1.1 API Support
here.
I'm not sure if appveyor vms have graphics cards, does it?
@matham Windows Server 2016
images run on GCE. AFAIK they use KVM hypervisor - I'm not sure what capabilities its video adapter provides. Do you get required OpenGL when running on default Visual Studio 2015
image?
@FeodorFitsner When is this planned to be available for all? Until then, I assume if I merge a commit adding the usage of this, everyone who doesn't explicitly have this enabled will have their forks break?
@FeodorFitsner so was trying to rdp to the server with the Windows server 2016 image, and something seems to be wrong with the printed rdp address. Windows says the address is wrong.
@matham RDP script has been fixed.
@nibanks we've just started collecting feedback. I don't have an exact ETA right now. We’d really like to understand what people might require on that image besides Docker and VS 2015 (we really don’t want dealing with VS 2013 stuff on that image). It could be in a week or so when it will become generally available.
@FeodorFitsner ran it again and the rdp is working again. So, no, I could not get opengl > 1.1 to work on Visual Studio 2015 image. I was hoping that server 2016 would add emulation so that you'd have opengl > 1.1 even if there was no GPU present, but it seems a GPU is required for opengl > 1.1.
GCE doesn't seem to have GPUs on the VMs you're running, so I guess that would not be possible.
Could you add EGAppVeyor
to the image as well?
@Crevil added
Hi @FeodorFitsner, just to check the following points with you. 1) Is the Windows Server 2016 installed on the WMF 5 image when indicated this is installed? If not, please advise which image I need to point my appveyor.yml file to reflect this. 2) Recent tests with my appveyor.yml on the WMF 5 configuration tells me no change mentioned earlier. PackageManagement\Install-Package : The version '0.7.13.51' of the module 'PScribo' being installed is not catalog signed. Ensure that the version '0.7.13.51' of the module 'PScribo' has the catalog file 'PScribo.cat' and signed with the same publisher 'CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US' as the previously-installed module '0.7.13.51' with version '0.7.13.51' under the directory 'C:\Program Files\WindowsPowerShell\Modules\PScribo\0.7.13.51'. If you still want to install or update, use -SkipPublisherCheck parameter. 3) As indication of the root cause appears to be "a Server 2016 cumulative update issue" affecting credential on the Powershell side. Is there a way to determine which version of Windows Server 2016 affecting this Thanks, Peter.
WMF 5 image is based on Windows Server 2012 R2.
Windows Server 2016
image should be enabled for your account before you can see/use it. Tell us your AppVeyor account name and we'll make this image available for you.
Hi @FeodorFitsner please could you enable the 2016 image on the sequensis account? Would love to try out some docker builds, thanks.
@neonboxx added.
@FeodorFitsner, ok then, my appveyor account is the same as Github name "PeterMTaylor". Thanks.
@PeterMTaylor added
A bit late to the party but would love to try docker builds too. My appveyor username is rickpowell131@hotmail.co.uk. Thanks
@rick-powell-sfw Added.
@IlyaFinkelshteyn Hi, I would also like to test docker build functionality, as it would help speed up the development process of our applications considerably. My appveyor username is matas@mediapark.com.
@MatZub Added!
Could you please add DDoSolitary
? Thanks!
@DDoSolitary added
Could you please add Pinata
? Thanks a lot!
@dgageot added.
@FeodorFitsner @IlyaFinkelshteyn can you add friism
please?
Hi, can you add TomerDvir as well? Thanks
Right now, we can build our Universal Windows App, but can't run any tests on AppVeyor.
Please add a Windows Server 2016 environment, now that RTM build have been available for a month.
(Note: We use shared code between our WPF and UWP projects, so we still need the older OS environments available as well.)
Updating Docker: