Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Windows Server 2016 Using VirtualBox: Getting Ready for Docker (Part 1)

DZone's Guide to

Windows Server 2016 Using VirtualBox: Getting Ready for Docker (Part 1)

If you're using Windows Server, the latest evaluation version is out for download. See how to configure your VMs in preparation for a multi-container Docker app.

· Cloud Zone
Free Resource

Production-proven Mesosphere DC/OS is now even better with GPU scheduling, pods, troubleshooting, enhanced security, and over 100+ integrated services deployed in one-click.

Windows  Server 2016 was announced a few weeks ago. To get a look at it, download the Windows 2016 Server Evaluation Version. This blog is the first part of a multi-part series. The first part will show how to set up Windows Server 2016 as a VirtualBox VM. This is an update to Windows Server 2016 using VirtualBox for Docker Containers.

  1. Download Windows 2016 Server Evaluation version.  It's around 5GB, so download it over a reliable and fast Internet connection.
  2. Create a new VM using Virtual Box: docker-windows-2016-1
  3. Set up a dynamically allocated HDD, make sure to choose 30GB (as shown): docker-windows-2016-2
    The installed operating system is ~17GB. The base windowsservercore image is 3.8GB. So if you chose the default 20GB HDD, then no Docker containers can run on it.
  4. Point to the downloaded ISO: docker-windows-2016-3
  5. Start the VM, take the default settings: docker-windows-2016-4
  6. Click on Next: docker-windows-2016-5Click on Install now.
  7. Select the Desktop Experience version, otherwise the standard Windows desktop will not be available after Windows is booted:
    docker-windows-2016-6Click on Next.
  8. Accept the license terms: docker-windows-2016-7
  9. Select Custom Install as we are installing as a VM: docker-windows-2016-8
  10. Take the default for the allocated space: docker-windows-2016-9
  11. Click on Next to start the installation: docker-windows-2016-10Wait for a few minutes for the installation to complete:docker-windows-2016-11It will take a few minutes for the install to complete.
  12. Enter the administrator’s password: docker-windows-2016-13Seems like it requires alphabets, numbers, and special characters. The dialog expects to meet the password criteria without showing the criteria. Yes, this is weird.
  13. Entering the credentials shows the Windows login screen: docker-windows-2016-14
  14. In a classical Windows, you do a three-finger salute of Ctrl+Alt+Del to view Desktop. This key combination needs to be sent to Windows VM using  Virtual Box menu: docker-windows-2016-15
  15. Server Manager Dashboard shows up: docker-windows-2016-16
  16. Latest updates need to be installed. Click on the Start icon, and search for update: docker-windows-2016-17Select Check for Updates.
  17. The update window looks like this: docker-windows-2016-18Select Check for updates again.
  18. Latest updates are downloaded and installed: docker-windows-2016-19
  19. Once the updates are downloaded and installed, then the VM needs to be restarted: docker-windows-2016-20Click on Restart now to restart the VM.
  20. Restarted VM looks like as shown: docker-windows-2016-21

This shows that Windows Server 2016 VM is now ready. Subsequent parts of this multi-part blog will show how to configure Docker containers and run a multi-container application using Docker Compose.

Simply build, test, and deploy. Mesosphere DC/OS is the best way to run containers and big data anywhere offering production-proven flexibility and reliability.

Topics:
docker ,cloud ,windows server ,virtualbox

Published at DZone with permission of Arun Gupta, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}