We are not done with containers yet. There are also Windows containers that are docker images running Windows as the host OS, from what I’m gathering and to add to the confusion you can throw Hyper-V in the mix, for some reason. I thought avoiding the resource usage of spinning up complete host images in a hypervisor was the entire point of containers? Currently, I’m not really sure but I’m excited to find out why you would use Hyper-V with a container. There are several questions on the MeasureUp info that are aliened with this but i’m going to quickly point out one for the sake of brevity. Ok maybe 2.
Ok, … a Hyper-V container but like aren’t we talking about Docker a whole bunch? Ok, right.
Please click the link and then check this MSFT trainers apparent literal installation of a ‘MSFT Kitchen’ haha. He is awesome by the way. He was also very instrumental in me learning so much foundational knowledge for Server 2012. However, I’m starting to wonder if there is any foundational knowledge on this test. Regardless, at least they haven’t asked any sub-netting questions yet. Please don’t do that, in the future. Math is not for people that are really proficient at installing server roles and features.
ok, any way. This seems like a good place to start. Meaning the link, before I started rambling. Noted that the video is full of what I call ‘Papa’s Promise’. For those unfamiliar with food chain advertising its full of nonsense that makes people feel like its quality. I’m not saying its not a good product but like these rubik’s cube situations in the video really got me. The other thing is they try to stay away from admitting that they didn’t invent this technology like ‘Container orchestrator’ and ‘Docker’ are clearly not the same thing. They go to go great lengths to prove this….
never gets old
Ok, so I have to say, I was on twitter the entire time it was playing, but the second video in this was immensely helpful as there some that actually does dev explaining this and the more I hear about it, its clear that some dev (well, this is the case with literally every thing in computers) was like ‘what if’ then followed up with a ‘hold my beer’ and gutted OS’s to bare bones and figured out a way to strip a VM down the bare bones for the hell of it. Honestly, who cares if company’s have to buy more hardware resources than they need to. I promise you the people that decided to do this did this because they thought it was fun. Or it was someone at a start up. Anyway, I mean, I don’t know much about ‘computer man’ culture but just taking a stab in the dark here. Ok, now to finish that first sentence with the hold my beer, so yeah like lets strip a VM down and make it run without the use of a hypervisor on a baseline application that runs faster and uses less resources because we have to get to 88 mph. Man, im starting to sound like the nomenclature when trying to listen to dev talk about ‘you see what we did here was strap this jownson outboard on the back of this there wheel barrow and on account of having more room in the main spot ‘dare we went ahead and put this turbo on it that Steve had done welded up the exhawst plumin for this thing on account of it being sat-er-dee and being bored. I know your thinking ‘you cant put a turbo on a damn 2 stroke’ but i tell uns what, we did’ kind of thing. Then the MSFT guy comes in and is like ‘and we here are msft are mad that we didnt think of putting a johnson outboard motor in a wheel barrow so we went ahead a bought a really fancy one. the two stroke with the turbo might be a bit much but we have this ‘proven’ motor that we may be able to repackage as its been tested for commercial use’ kind of thing. Ok, so I like containers. This is fun. And no, I did not grow up around red necks that would do that sort of thing in the out skirts of Atlanta in somewhat rural area with a father that worked on cars for a living, thanks for asking. Anyway, besides the initial excitement of hearing someone who builds these things discuss implementing and testing hot fixes in a sandbox type environment with an even lighter weight product than a virtual machine to blow up and rebuild, I still have no idea what Hyper-V is doing in this. Using Nano server and so forth to build a container image upon makes sense but i’m still in for more reading as to not, why (we figured that one out…), but how we are using Hyper-V with…containers…which are supposed to avoid having a complete VM. So, lets get to that.
Hyper-V isolation – multiple container instances can run concurrently on a host, however, each container runs inside of a special virtual machine. This provides kernel level isolation between each container as well as the container host.
So basically what your saying is its, plausibly more armored (its not) but uses more resources? Ok, I’ll go with it and memorize the answers. My favorite part is that examples are PowerShell cmds in the article haha ok. There is also the factor of using Hyper-V makes people think these are VMs, a highly confusing thing, which they are not. Thinking in that fashion will do you no favors.
Windows Server 2016: Windows Containers vs. Hyper-V Containers
Now they want to get specific. Good. Lets check out this applesauce, I hope it has cinnamon in it because that’s the best kind.
This is now starting to make sense as it provides kernel isolation with Hyper-V to ensure that OS updates don’t break the code. However, this can be mitigated easily by sand-boxing OS updates and updating code accordingly. Which is common practice. Besides if you update and break it apparently takes less time to spin up an new instance of the same container. So I’m not exactly clear on specific instances of why one would actually need to use this in production. MSFT is starting to see that, “starting” (lol), to see that Linux servers are easier to maintain as web servers and not to mention cheaper. It’s an important market share to not miss out on however most of the people that are actually building things out like this cannot afford to buy a server data center license for their home brew shit. I feel like there is an apple joke about monitor stand coming into play. Right about, now.
Its an important market share and I understand it. I’m honestly not convenienced on the need for the tech tough.
So this is an interesting link that is one this second question that I’m finally getting around to posting. Now that I have successfully discussed every thing but the actual answer to the previous question. Its sort of what I do, sorry. Oh, its also somewhat related to the other question. Any way here is that link
Windows container requirements
Specifically the table in that article basically contains the answers. Now that we have figured out the why, knowing the answer without know why isn’t fucking annoying. The interesting part is that they very clearly state the difference in sizes of the containers I’m realizing that compared to a file size of well over a gig for a full VM this isnt that bad.
Nano Server (os only) 40 MB (Hyper-V install) 130 MB + 1 GB Pagefile
Until you get to that paging file bullshit. Come on, really? There is some further information thats interesting but I’m not that clear on actual app building and dlls and slimmed down versions of .NET (lol) so I’m going to stick with what we’ve got. I do honestly feel like I now understand the differences and am happy to memorize answers to things that I have a grasp on the concept of the technology.
Leave a Reply