Saturday morning Docker fun times (still only on Windows Server Core) - here is something I found out that might be useful. It is in the Docker documentation but it is not mentioned in the Microsoft container documentation.
Once you have attached to a Docker Container via a CMD console typing exit at the console detatches from the container and Stops it. This is not usually what I want to do.
Something quick for Friday morning! Are you feeling enthusiastic about DSC? Do you want to update or install every DSC resource in a repository onto your computer?
Try this (only on PowerShell 5.0 computers - what do you mean you’re not using PowerShell 5.0?):
[sourcecode language=“powershell”] Find-DscResource | Select-Object -ExpandProperty ModuleName -Unique | % { Install-Module -Name $_ -Force } [/sourcecode]
This will download and install (or update if you’ve got older versions) of all DSC Resources in all PowerShell Repositories registered on your computer.
This is a continuation of my investigation of how to get Containers and also possibly the Docker engine running on Windows Server Nano 2016 TP 3. The initial investigation into this can be found here: How to use Containers on Windows Nano Server.
This post is mainly documenting the process of manually creating containers on Windows Nano Server 2016 TP3 as well as some additional details about what I have managed to find out.
Edit: I wrote this article when examining containers on Windows Nano Server TP3 - which wasn’t in a working state. I have not yet had a chance to fully examine containers on Windows Nano Server TP4, but when I get a spare day hours I will no doubt deep dive into it.
If you’re looking for instructions on installing and using containers on Windows Nano Server TP4, start here.
These instructions are more focused on setting up a container host on Windows Server Core TP4, but I have managed to get them working on Windows Nano Server TP4 just fine:
