If so, what vm image can I use?
This is purely for development purposes, and to simply run dev workloads on an azure VM that I can spin up and down as needed.
Docker CE for Windows says "Docker for Windows requires Windows 10 Pro or Enterprise version 10586, or Windows server 2016 RTM to run"
I just need a reasonable substitute than running locally since I am running windows 10 HOME on my laptop and would like to run Docker CE somewhere that actually works 100% of the time.
I tried the [Windows Server 2016 Datacenter with Containers] image that #win mentioned below, but it has enterrpise edition already installed out of the box, not CE
You need to use Windows Server 2016 Datacenter with Containers.
Related
Our goal is to run UI tests with Appium on our CI build. But it seems that running the Android emulator (Hyper-V based) within virtual build machine (Windows Server 2016) on Azure might not be supported.
So my question is, does Hyper-V based nested virtualization is supported from a Windows Server 2016 virtual machine on Azure ?
note: using a CPU Android emulation is not an option
Yes, it is possible, you need to be on Dv3 or Ev3 SKU.
https://learn.microsoft.com/en-us/azure/virtual-machines/windows/nested-virtualization
I want to create a ASP.NET Core 2.0 website in a docker container and host it on a Linux VPS docker system. I tried creating an ASP.NET Core 2.0 project in Visual Studio, and then publishing it to docker hub. Everything works great, until I want to run that docker image on my Linux environment. I then get an error saying that this image is created for windows or something equivalent. I know I need to create the asp.net project in the Linux environment, then start coding (obviously), but I want to do the coding in for example Visual Studio on my PC, not via PICO or some other ssh-connected editor.
Summarized:
- I wish to run ASP.NET Core 2.0 website on Linux Docker VPS environment.
- I (think I) need to create the project in the Linux environment (I run Windows locally).
- Wish to edit the code in the docker container locally on my Windows environment.
Anyone know how I can achieve this?
Before creating ASP.NET Core 2 website on your windows operating system, right click on the Docker icon in system tray and then click Switch to Linux containers. Once switched to Linux containers, create ASP.NET Core website that you can host on Linux.
I am trying to get Debian working in the host Windows Server 2012 R2. The Windows Server is running on other host, macOS with Parallels. I am getting the following error One of Hyper-V components is not running. Debian 9.1.0 is not listed in the supported VMs here and only older Debians are mentioned, could this cause the error?
How to resolve this error One of Hyper-V components is not running?
You are attempting to run Hyper-V as a nested hypervisor. It must have recognized that Parallels doesn't expose required features to Windows Server VM and hence, Hyper-V hypervisor itself is not running.
Have a look at Server manager and\or event log on Windows Server, it will most probably have an error, explaining that required hardware features are not present on the host to start Hyper-V.
Parallels describes how to enable Nested virtualisation support in this Knowledge Base article on their official site.
I'm trying to use Packer form Hashicorp to create VMs. The idea is that I can create Windows 10 VMs for for each of my assignments, and run those VMs on my "main" Windows 10. I have access to Hyper-V, and as of late 2016, Packer supports that too.
Grabbing several files from Matt Wrock's Github repository, I have created a json file, an Autounattend and some scripts. When running Packer, I ended up with an error saying "Error getting WinRM host: No ip address". This had gone on for 5+ hours, so something was not going right. Interestingly, the Hyper-V Manger said that the VM was there, and I could even log in. Then I noticed that none of install scripts had been executed. For instance, in my Autounattend I execute Matt's boxstarter.ps1 script to install Boxstarter, but Boxstarter has not been installed.
To get a better visual on the process, I changed the Autounattend.xml to have all WillShowUI properties set to true. Nothing appears. To me this seems like Windows 10 is not booted. Any idea how I can check this? Also, from a different Github repository, I found in a json file for Windows Server 2013 the "boot_command" with value aaa. Without having any idea whether this applies to Windows 10 as well, I put that in my json file too. Maybe this boot command is wrong?
Alternatively, is there anyone out there having a public repository which I can use to create Windows 10 VMs that will run on Hyper-V on a Windows 10 machine?
Got some good news :) You don't need to build Packer from source for the Hyper-V provisioner. It was merged in at version 0.12.1 so if you have the latest you're good to go.
Here are some samples that I used when testing it for version 0.12.1+:
https://github.com/StefanScherer/packer-windows - Samples for Windows 10 & Windows Server 2016 set up with Docker & Windows containers
Ubuntu 16.04, hyperv-iso, generation 2 (UEFI) https://github.com/taliesins/packer-baseboxes/blob/master/hyperv-ubuntu-16.04.json
Feel free to ping me on GitHub (#patricklang) with issues in any of those repos.
There is not enough details to tell what's wrong.
Try using taliesins basebox - Windows 10, he is the main author of the Hyper-V support in Packer and I expect his examples to work.
I am trying to setup a Windows 7 Virtual Machine in Azure and I see a list of Windows Server options, but not a plain Windows 7 Professional.
I need Windows 7 for testing purposes.
Do they only support server VMs?
Edit: After Searching I found that Windows 7 Enterprise N is supported. I guess I could use that. But it seems lame that they would not support something so common as Windows 7 Professional...
Windows 7 (and all Windows client OSs) are not supported, or more importantly, licensed for use on ANY cloud service.
Azure gets around this limitation by only allowing Windows Client machines to be run as MSDN development machines. (I imagine being Microsoft helps too)
If you have an MSDN subscription, you will have access to Win7, Win8, and Win10 machines.
So if you wanted to build a business running Windows client machines, licensing would restrict that, but if you're using it as a development machine, that is ok.
So you couldn't, for instance, give everyone in an office access to a Win 10 Machine on Azure.