Skip to main content

Server 2016: Multi Interfaces Per NIC (Short); Docker For Windows Server (Longer)



Adding more than one IP address to an interface, just incase said interface is being woefully underused. This is a good way to use avaliable resources.

The primary interface is Ethernet, with an Index of 2.




There's no need to set the gateway, as these are all in the same subnet. There's also no Windows-Imposed limit. Your only limit is your imagination (and hardware).

Although I can add IP addresses, they want me to set up the Server properly before I can finangle with NIC teaming.



There are two starter users; Rosanta Galamad and Juke Morrow. The latter is an Administrator. The folder added is a gussied-up test folder.

Meanwhile, I pop ahead in the textbook (MSCA 70-740 Cert Guide) to see - A Docker chapter! We can do that! (If we get the internet working properly in the server - What happened?)

But we can install it on our host machine. Why not?





As you know, WS16 containers are about Isolation, each container has it's own view of the host, and they have kernel sharing.

Kernel mode is not shared with the Hyper-V, but it is connected to a container, and that container is surrounded by a H-V container with Hardware Assisted Virtualization, and that's connected to a user mode.

Look at it like this;

Kernel mode <---------> (Hyper-V [Container] Hyper-v) <---------> User Mode

There are

  • Container shared folders
  • Resource restrictions
Sandboxes are where modifications happen after a container starts.

Windows based container images have build hashtags that must match between the container and the operating system. These images run on Server Core and Nano Core.

The Container and Host are connected to the base and kernel, but not to each other.

✅ Your Version
HKEY_LOCAL_MACHINE\software\Microsoft\WindowsNT\Current Version

✅ Your Base Version and the Hash Table

You could mismatch host and image versions but they may not work properly, so why do it?

To download Docker through Powershell, Run as Admin and there's a code with syntax (See above).

The ENGINE is;

  • How the Daemon accepts requests
    • (Or the appropriate config file C:\ProgramData\Docker\Config\daemon.json)
    • (or sc config in PS)
  • How it networks
  • Debug/Logs
Deploy a Host by Installing the Base Image in Core or Nano.

Hyper-V Containers
  • Enable Nested virtualization on parent machine.
  • You can do this in PS Elevated with install-windowsFeature hyper-v
If you're trying to install something and it says 'install module not found', time to go back to the good old Linux days of hunting for the appropriate package to download.

Commands For Container Management;

Docker ___________
  • run (-it, a pseudo shell connected to a container)
  • ps (List of containers on host)
  • start
  • stop
  • attach (to a session on a running container)
  • rm (remove)
  • commit (new image)
These have the suffix -Container. Ex, get-container

Get- (list of containers on Host)
Start-
Stop-

Enter-Container Session


Labels:

Comments

Post a Comment

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H
Post a Comment
Read more

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory
Post a Comment
Read more

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.
Post a Comment
Read more