Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements


fanbaby fanbaby
  • Window container support on client

    In any case, it makes little sense to deploy windows container to a Windows VM running under Linux vs deploying to a windows server directly.

  • Window container support on client

    @evildictaitor: I think you're confusing a benefit of containers and the reason they exist. Containers were created to be better then VMs in start time, overhead, memory use and general efficiency. Assuming that, it makes very little sense to do what you describe, save for development purposes, For example if you have a windows machine and develop linux containers (boot2docker).

  • Window container support on client

    @evildictaitor: isn't the point about containers that you don't run a full VM? What's the point of running a Windows VM under Linux in order to run a Windows container? Just skip the Linux os!

    Build your windows containers to your heart content, just know that you must have windows to run them (don't forget to take licensing into account :)). I just want to add that you must have a good reason to do that (as apposed to creating a Linux container).

  • Window container support on client

    This (containers), windows 10 for arm boards (like the raspberry pi) and windows nano will suffer the same fate as Silverlight. If you are a Windows developer hoping these technologies will save from the burdon of learning unix-like tools and technologies, don't waste time on them.


  • Window container support on client

    @kettch: There's no such thing as a 'docker container'! There's a docker linux container and soon docker windows container.

    When you write a (binary) application, you either use Win32 or POSIX apis. You cannot run a posix app in a windows container (not without a linux VM that is).

    EDIT: and my advice: unless you are leveraging a big WIn32 code base, do not embark on developing new Win32 container.

    ANOTHER EDIT: You cannot be a developer in 2015 without knowing linux.

  • Window container support on client

    , kettch wrote

    In one of the sessions (it might have been C9 Live), Mark Russinovich deploys an application to a container on one OS and then moves the container to another OS and it works just fine. It's not virtualization, it's just that Windows now exposes the API's needed to allow the Docker abstraction to work.

    Not so. Windows Server will not run Linux containers without a VM running Linux. See my previous post here. Check this out, forward to the 15:00 mark:



  • Window container support on client

    I'll be really surprised if Linux containers run directly on Windows Server (i.e. without some form of virtualization). Any details and references are welcome.

    Will this fare better than the POSIX layer of yore?

  • Window container support on client

    Bass, if I understand you correctly, you think that there's a 'universall' docker container format. There's no such thing. There's currently a Linux container, and in the near future, there'll be a Windows container. Linux containers run on Linux (either normal Linux or under a VM in Windows), and windows containers will run on Windows. Whether it needs Windows  Server or not, I don't know.

  • Raspberry Pi and Windows 10 hands on

    @cbae: You're right. I have not completed my mcsd therefor i take back my statement.


    "2015 - eschewing linux/bash is the modern form of dev illiteracy" - me

  • Raspberry Pi and Windows 10 hands on

    Advice to anyone investing time on this: most probably you're wasting your time. If you're not familiar with bash and linux, learn them instead. If you already know linux/bash etc, happy hacking windows 10 on this, carry on :)