Earlier quoted context omitted.
There used to be Windows Services for UNIX (a.k.a. Subsystem for UNIX-based Applications): http://en.wikipedia.org/wiki/Windows_Services_for_UNIX https://technet.microsoft.com/en-us/library/cc771470.aspx
They ditched in Windows Server 2012. Now recommend cygwin. "The Subsystem for UNIX-based Applications (SUA) is deprecated. If you use the SUA POSIX subsystem with this release, use Hyper-V to virtualize the server. If you use the tools provided by SUA, switch to Cygwin's POSIX emulation, or use either mingw-w64 (available from Sourceforge.net) or MinGW (available from MinGW.org) for doing a native port. " https://tec…
Microsoft announces Hyper-V Containers
91–100 of 148 posts
Re: Microsoft announces Hyper-V Containers
#92Pardon the skepticism, but do "Hyper-V Containers" with "enhanced isolation powered by Hyper-V virtualization" sound suspiciously like, err, Hyper-V virtual machines? And "Server Nano" has a description rather reminiscent of 2008's "Server Core". Is this just about management tools? Because that's cool, too, but why the spin?
From the TechNet Announcement: "we removed the GUI stack, 32 bit support (WOW64), MSI and a number of default Server Core components. There is no local logon or Remote Desktop support. All management is performed remotely via WMI and PowerShell. We are also adding Windows Server Roles and Features using Features on Demand and DISM. We are improving remote manageability via PowerShell with Desired State Configuration…
Wow, I've been out of the Windows world for years, can you really fully manage a Windows box without the GUI?
Re: Microsoft announces Hyper-V Containers
#93Earlier quoted context omitted.
And where FreeBSD did jails in 2000 (or actually a bit earlier). https://www.freebsd.org/releases/4.0R/notes.html
Yes, everyone refers to jails, but I think most people would agree that jails weren't really containers. They didn't provide true isolation for a set of applications. I guess you could argue they were the original prototype for them though. Solaris containers are the first "lightweight virtualization" technology that I'm personally aware of that provided true isolation of one more processes from the host operating sy…
http://en.wikipedia.org/wiki/VM_%28operating_system%29
There are a lot of things from the mainframe world that are being newly "discovered" that seem quite mundane to the greybeards...
http://en.wikipedia.org/wiki/IBM_System_z#Comparison_to_othe...
Re: Microsoft announces Hyper-V Containers
#94Pardon the skepticism, but do "Hyper-V Containers" with "enhanced isolation powered by Hyper-V virtualization" sound suspiciously like, err, Hyper-V virtual machines? And "Server Nano" has a description rather reminiscent of 2008's "Server Core". Is this just about management tools? Because that's cool, too, but why the spin?
It means their memory isolation is using hardware accelerated extensions. I would imagine it's still shared kernel and thus not "virtual machines". It makes sense for their container solution to make use of existing Hyper-V components like the virtual switch etc. But for that to be possible it's likely they needed to make use of VT-x and VT-d (if using stuff like hardware accelerated network device isolation like SRI…
Re: Microsoft announces Hyper-V Containers
#95What filesystem backend does docker use on Windows? Doesn't it require a copy on write filesystem to be efficient?
We're building a new one as part of the Windows Server Container implementation. Also doing copy-on-write registry and tightening up Job Objects: https://msdn.microsoft.com/en-us/library/windows/desktop/ms6... With any OS, containers are actually made up of several low-level components put together behind a management experience (which will include Docker).
Re: Microsoft announces Hyper-V Containers
#96Earlier quoted context omitted.
Thanks a lot for your answer. We create a separate container for each application, as it seemed like the correct approach. In our company we do have several "levels" of library (even jvm) version requirements. Containers have been very helpful to easy the pain that was managing that on the server side.
I've found that building fat JARs with all dependencies bundled solves a lot of the same dependency management issues containers can be used for. And it does it without container overhead.
Re: Microsoft announces Hyper-V Containers
#97Earlier quoted context omitted.
Yes, everyone refers to jails, but I think most people would agree that jails weren't really containers. They didn't provide true isolation for a set of applications. I guess you could argue they were the original prototype for them though. Solaris containers are the first "lightweight virtualization" technology that I'm personally aware of that provided true isolation of one more processes from the host operating sy…
Not sure if "lightweight" counts when talking about a mainframe, but when first encountering Solaris zones they seemed equivalent to LPAR's in the mainframe world. http://en.wikipedia.org/wiki/VM_%28operating_system%29 There are a lot of things from the mainframe world that are being newly "discovered" that seem quite mundane to the greybeards... http://en.wikipedia.org/wiki/IBM_System_z#Comparison_to_othe...
The equivalent to LPARs in the Solaris world would be LDOMs on SPARC.
Re: Microsoft announces Hyper-V Containers
#98It'd be nice if Visual Studio tooling could let you hit F5 and your app could Compile, Deploy to an On-Desktop Container after running a dockerfile, Start Debugging from a 'remote' debugger.
Re: Microsoft announces Hyper-V Containers
#99Top it off with SSH access to PowerShell and we're all set? (Something something something dark side)
Yes please. And native rsync interoperability too? I've love to banish cygwin from my Windows servers. Although I'm finding the remote powershell execution from a Linux machine use case is now handled quite well by tools like Salt (via ZeroMQ to the minion) and Ansible (via WinRM). Native SSH would still be good though for tunnelling etc.
Hear, Hear! You and me both. I've never liked Cygwin and do my best to avoid when possible.