Containers are isolated environments to run applications or make configuration changes without affecting the Windows Host or Host configurations. Containers are not Virtual Machines. A Container Management layer is added between the operating system and applications. There is only one operating system unlike with Virtual Machines that have a separate OS installed on them.
You must enable Container Support, then the Container Management layer is added between the OS and the different containers.
Some advantages of containers include
portability (easy to move without impacting the Host OS),
disposability (easy to delete containers without impacting the Host OS),
licensing (you do not need a separate license per container unlike VMs that need a separate license per OS installed).
You can create Windows Server Containers which are used to isolate applications so each has its own view of the host OS, or you can create Hyper-V Containers which are based on the hardware-assisted virtualization provided by the Hyper-V hypervisor.
The name of the software you need to download and install is called Docker.
Container Storage is not persistent. If the container is shut down, then any changes made within a running container are lost. You can create an image file that captures the container’s configuration and file system changes, or mount a directory in the container host’s file system in the file system of the container.
You can configure NAT to do address translations between the container’s private addressing to the physical network segment.
You can configure a Transparent network where there is a connection directly to the physical network segment to allow addressing through DHCP directly to the container’s virtual adapter.
You can configure an L2 network that uses Layer 2 tunneling between networks.