Scribd
Upload
186 views8 pages

NAV Docker Documentation

Virtualization and Hyper-V must be enabled and installed for Docker Desktop to run, as it requires these features. Docker Desktop uses Hyper-V to create and run Windows containers, so Hyper-V, virtualization, and sufficient RAM must be configured properly. Images for Docker include version, cumulative update level, and localization in the tag to identify the specific Dynamics NAV installation package.

Uploaded by

Gelu Moldovan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
186 views8 pages

NAV Docker Documentation

Virtualization and Hyper-V must be enabled and installed for Docker Desktop to run, as it requires these features. Docker Desktop uses Hyper-V to create and run Windows containers, so Hyper-V, virtualization, and sufficient RAM must be configured properly. Images for Docker include version, cumulative update level, and localization in the tag to identify the specific Dynamics NAV installation package.

Uploaded by

Gelu Moldovan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
You are on page 1/ 8

Virtualization

For Docker Desktop to function correctly, your machine must have the following features:

1.Hyper-V installed and working

2.Virtualization enabled

HYPER-V

Docker Desktop requires Hyper-V as well as the Hyper-V Module for Windows Powershell to be installed and
enabled. The Docker Desktop installer enables it for you.

Docker Desktop also needs two CPU hardware features to use Hyper-V: Virtualization and Second Level
Address Translation (SLAT), which is also called Rapid Virtualization Indexing (RVI). On some systems,
Virtualization must be enabled in the BIOS. The steps required are vendor-specific, but typically the BIOS
option is called Virtualization Technology (VTx) or something similar. Run the command systeminfo to check all
required Hyper-V features. See Pre-requisites for Hyper-V on Windows 10 for more details.

To install Hyper-V manually, see Install Hyper-V on Windows 10. A reboot is required after installation. If you
install Hyper-V without rebooting, Docker Desktop does not work correctly.

From the start menu, type Turn Windows features on or off and press enter. In the subsequent screen,

verify that Hyper-V is enabled:


HYPER-V DRIVER FOR DOCKER MACHINE

The Docker Desktop installation includes the legacy tool Docker Machine which uses the old boot2docker.iso, and
the Microsoft Hyper-V driver to create local virtual machines. This is tangential to using Docker Desktop, but if
you want to use Docker Machine to create multiple local Virtual Machines (VMs), or to provision remote
machines, see the Docker Machine topics. This is documented only for users looking for information about
Docker Machine on Windows, which requires that Hyper-V is enabled, an external network switch is active,
and referenced in the flags for the docker-machine create command as described in the Docker Machine driver
example.

VIRTUALIZATION MUST BE ENABLED

In addition to Hyper-V, virtualization must be enabled. Check the Performance tab on the Task Manager:

If you manually uninstall Hyper-V or disable virtualization, Docker Desktop cannot start. See Unable to run
Docker for Windows on Windows 10 Enterprise.

Trimis de Horatiu

https://forums.docker.com/t/missing-options-in-the-settings-menu/55316
Install and configure Docker
Install Docker and configure it for Windows Containers.

Please choose the version of Docker that is appropriate for the host operating system.

Use Docker Community Edition if the host operating system is Windows 10.
For more information, see Install instructions.
Use Docker Enterprise Edition if the host operating system is Windows Server.
For more information, see Install instructions.
Switch Docker to use Windows containers. By default Docker uses Linux containers.

To switch to Windows containers, in the Taskbar, right-click the Docker icon Docker, and then select Switch to
Windows Containers. For more information, see Switch between Windows and Linux containers.
docker pull microsoft/dynamics-nav:2018-cu14
cls

docker run -e accept_eula=Y -m 4G microsoft/dynamics-nav


docker run -e accept_eula=Y microsoft/dynamics-nav -eroare

At least 3Gb memory needs to be available to the Container.


At C:\Run\start.ps1:27 char:5
+ throw "At least 3Gb memory needs to be available to the Container ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (At least 3Gb me... the Contai
ner.:String) [], RuntimeException
+ FullyQualifiedErrorId : At least 3Gb memory needs to be available to the
Container.

docker run -e accept_eula=Y -m 4G microsoft/dynamics-nav:2018-cu14

docker inspect microsoft/dynamics-nav:2018-cu14 -afiseaza date network settings

docker ps -a - -Show all containers (default shows just running)


docker rm <ContainerID> - remove Container with ContainerID

docker images -a -- Show all images (default hides intermediate images)


docker rmi [IMAGEID] - remove Image with ImageID

CTRL + C - treminate docker run command

docker run -e accept_eula=Y -e accept_outdated=Y -m 4G microsoft/dynamics-nav


-RULEAZA dar nu se poate deschide in browser
-e = cred ca se pune in fata la fiecare optiune
-m = memmory minim 4G

Docker image names are build up of 3 sections:


<registry>/<repository>:<tag>
<registry> can be a private registry (like navinsider.azurecr.io) or the public docker hub, using a single
identifier (like microsoft).
<repository> is for all NAV images dynamics-nav
<tag> determines which NAV image to get.
The tag is build up by this syntax: [[version][cu]][localization]
All parts of the tag are optional and if you omit a part, you will get the latest (or w1 for the localization).
Parts are seperated by a dash if multiple parts are specified and all parts are specified using lower case
characters.
Disk space resource.

1. inainte de orice pull docker

2. docker pull microsoft/dynamics-nav

diferenta ~ 16.9 GB
3. docker pull microsoft/dynamics-nav:2017-w1

diferenta ~ 1.2 GB

You might also like