How to use this box with Vagrant:
Vagrant.configure("2") do |config|
config.vm.box = "mwrock/WindowsNano"
end
vagrant init mwrock/WindowsNano
vagrant up
This version was created over 6 years ago.
Cleanup updates and shring down ~200MB.
This version was created over 6 years ago.
Install updates
This version was created over 6 years ago.
Updated to RTM. Fixes bluescreen on first boot in hyper-v
This version was created over 6 years ago.
TP5 and adds -Containers and IIS and DSC packages
This version was created over 6 years ago.
Built with Technical Preview 5
There is a known issue on the Hyper-V provider where it blue screens on first boot. This goes away after a reboot.
This version was created about 7 years ago.
Updates to Technical Preview 4
This version was created about 7 years ago.
Edits the vagrant user so its password never expires.
This version was created over 7 years ago.
This is a Windows Nano Technical Preview 3 box.
The WinRM service in Nano currently only accepts requests set to the UTF-8 code page 65001. However, the WinRM Gem used by Vagrant sets the codepage to 437. This prevents vagrant from establishing WinRM connections with the nano box.
However, Vagrant is able to create and destroy the box and one can connect via via windows Powershell Remoting.
The very first boot on Hyper-V will blue screen. However it will recover. How it recovers depends on the type of switch used:
You can connect via powershell remoting using port 55985 on VirtualBox and the normal WinRM ports using Hyper-V.
More instructions to come
This box was created using the template located at https://github.com/mwrock/packer-templates/blob/master/vbox-nano.json The build was identical for VirtualBox and Hyper-V with the exception of the drivers used to create the initial nano image. Hyper-V used the -GuestDrivers
option and VirtualBox used -OEMDrivers
.