windows
docker-ee
[!WARNING]
OneGet/MicrosoftDockerProvider
[#65: [PROXY] Cannot find path 'C:[..]\DockerMsftProvider\DockerDefault_DockerSearchIndex.json' because it does not exist.](https://github.com/OneGet/MicrosoftDockerProvider/issues/65)
IMPORTANT - THIS PROVIDER IS NOW DEPRECATED
As of May 23rd 2023 the backing service for this provider has been shutdown. You can find alternative options at [Windows Container Documentation - Setup Environment](https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=dockerce#windows-server-1). For more information on the deprecation please see the following blog posts: [Updates to the Windows Container Runtime support](https://techcommunity.microsoft.com/t5/containers/updates-to-the-windows-container-runtime-support/ba-p/2788799) [Reminder - Updates to Windows Container Runtime Support](https://techcommunity.microsoft.com/t5/containers/reminder-updates-to-windows-container-runtime-support/ba-p/3620989)
install
[!NOTE] references:

install specific docker version
check
check module and resource
update DockerMsftProvider
upgrade to latest version
or to particular version
pull and run windows image
install a specific version
upgrade
via daemon.json
verify
via SSL
allow inbound connections
copy the files
ca.pem,cert.pemandkey.pemfrom your user's docker folder on your machinee.g.
c:\users\chris\.dockerto you local machine.
confirm connection
tips
disable tls in
c\programdata\docker\config\daemon.jsonconnect via
exec commands
[!NOTE|label:references:]
image discovery
Base images for Windows Insiders
[!TIP]
Windows Server Core vs Nanoserver
Windows Server Core and Nanoserver are the most common base images to target. The key difference between these images is that Nanoserver has a significantly smaller API surface. PowerShell, WMI, and the Windows servicing stack are absent from the Nanoserver image.
tricky
running linux container in windows server
[!NOTE]
by enable experimental features in docker daemon.conf
Set LCOW_SUPPORTED Variable to 1 for enabled
enable experimental features in docker
daemon.confdeploy LCOW for it to run
make Linux containers the Default
uninstall current docker-ee
enable Nested Virtualization by using Linux Virtual Machine running on Hyper-V.
install pre build docker-ee
Enable LinuxKit system for running Linux containers
to Switch back to running Windows containers
restart docker service
check
[!NOTE]
download archive
install
DockerMsftIndex.json
[!NOTE]
dockerfile
[!NOTE|label:references:]
sample
sample
or
Hyper-V
[!TIP|label:references:]
install
in windows servers
[!TIP] If you're connected locally to the server, run the command without
-ComputerName <computer_name>.
via commands
check
manually
In Server Manager, on the Manage menu, click
Add Roles and Features.On the Before you begin page, verify that your destination server and network environment are prepared for the role and feature you want to install. Click
Next.On the Select installation type page, select
Role-basedorfeature-basedinstallation and then clickNext.On the Select destination server page, select a server from the server pool and then click Next.
On the Select server roles page, select
Hyper-V.To add the tools that you use to create and manage virtual machines, click
Add Features. On the Features page, clickNext.On the Create Virtual Switches page, Virtual Machine Migration page, and Default Stores page, select the appropriate options.
On the Confirm installation selections page, select
Restart the destination server automatically if required, and then clickInstall.When installation is finished, verify that Hyper-V installed correctly. Open the All Servers page in Server Manager and select a server on which you installed Hyper-V. Check the Roles and Features tile on the page for the selected server.
in windows 10
[!NOTE] references:
via powershell
check

via cmd and dism
via manually
win -> Apps and Features
select Programs and Features
select Turn Windows Features on or off
Select Hyper-V and click OK

enable hyper-v in settings others
shortcut located in :
shell:Common Administrative Tools(C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools)Hyper-V Quick Create :
%ProgramFiles%\Hyper-V\VMCreate.exeHyper-V Manager :
%windir%\System32\mmc.exe "%windir%\System32\virtmgmt.msc"
troubleshooting
[!NOTE]
solution
or
Last updated