Skip to Content

Changes for page Install Docker for Linux

Last modified by Erik Bakker on 2025/04/18 13:54
From version 13.1
edited by eMagiz
on 2022/10/28 12:21
Change comment: There is no comment for this version
To version 3.1
edited by eMagiz
on 2022/06/24 14:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,32 +16,18 @@
16 16  
17 17  == 3. On-premises deployments ==
18 18  
19 -===3.1 Installation requirements Windows Server 2019 version 1806===
19 +===3.1 Installation requirements
20 +Below the list of requirements for an on-premises deployment
20 20  
21 -Below the installation step for this version of Windows
22 -
23 -* Enable Hyper-V in Windows Server
24 - ** Go to Server Manager, Manage (top right), enable roles and features, select the desired roles and server selections. In the Features section, enable Hyper-V.
25 - ** Restart windows
26 -* Install Docker Desktop on the Windows Server
27 - ** Please refer to this link: https://www.docker.com/products/docker-desktop/
28 - ** Restart windows
29 -* Update Docker desktop configuration
30 - ** Go to settings, and enable ‘Expose daemon on tcp://localhost:2375’ without TLS
31 - ** Restart Docker
32 -* Open Powershell as Administrator
33 - ** Execute "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchLinuxEngine
34 - ** Execute Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
35 - ** Execute curl.exe -L -o ubuntu-2004.appx https://aka.ms/wslubuntu2004
36 - ** Execute Add-AppxPackage .\ubuntu-2004.appx
37 - ** If errors occur, please consult https://learn.microsoft.com/en-us/windows/wsl/install-on-server. Rename the file to a zip, expand it, and add it to the path variable.
38 -* Ubuntu should now be a runnable program (press windows key, type ubuntu)
39 -* Open the ubuntu terminal, and finish the installation.
40 - ** After installation, execute: export DOCKER_HOST=tcp://localhost:2375
22 +* Windows Server or Linux Server
23 +* Installed Docker software
24 +* Server connected to the internet whereby the firewall doesn't prevent data traffic going outwards to the Internet
25 + ** In case there are outgoing firewall rules, eMagiz can provide the specific URL's and port numbers in order to update the firewall
26 +* Sufficient resources inline with the requirements of the eMagiz runtimes. See this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory.WebHome||target="blank"]]
41 41  
42 42  === 3.2 Installation agent ===
43 43  
44 -eMagiz needs to install a specific agent in the Docker instance that allows to download runtime images that needs to be installed on the Docker instance. The specific command to run inside the Docker instance is specific for the machine that is configured inside eMagiz Design & Deploy Architectures. It can be found inside the eMagiz iPaaS portal or is available upon request. Once that agent is installed, the image that is generated for every eMagiz release can be downloaded and installed in the Docker instance.
30 +eMagiz needs to install a specific agent in the Docker instance that allows to download runtime images that needs to be installed on the Docker instance. The specific command to run inside the Docker instance is specific for the machine that is configured inside eMagiz Design & Deploy Architectures. It can be found inside the eMagiz iPaaS portal or is available upon request.
45 45  
46 46  === 3.3 Cloud architecture for API Gateway ===
47 47  
... ... @@ -49,22 +49,24 @@
49 49  
50 50  == 4. Assignment ==
51 51  
52 -Check out the cheatcheet for Docker command line:
53 -
54 -[[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]]
38 +There is no specific assignment for this microlearning.
55 55  
56 56  == 5. Key takeaways ==
57 57  
58 -* eMagiz uses runtime images to deploy emagiz runtime on dockerized environments. The runtime image holds all the information and components required to run the runtime
59 -* eMagiz has a specific agent that manages the download of that image to the on-premises server
60 -* The firewall of the on-premises environment should allow outgoing traffic without any restriction. In case that is not desirable, eMagiz can provide the addresses and ports needed to setup the right firewall rules.
42 +* eMagiz will help to determine the needed memory via the Design Architecture page.
43 +* eMagiz works with pre-determined sizes that are represented via an S, M, L, XL structure. Every size has a certain amount of memory available
44 +* When you exceed such a threshold you should upgrade (or downgrade) your memory in consultation with your partner manager
45 +* Overhead for OS and support functionality (auto-healing, alerting, monitoring) needs to be taken into account
46 +* Calculating memory can be challenging. Always confer with others before taking action
47 +* You can compare your calculations with the calculations of eMagiz
48 +* The calculations and logic described below are applicable for the Messaging, API Gateway and Event Streaming pattern
61 61  
62 62  
63 63  
64 64  == 6. Suggested Additional Readings ==
65 65  
66 -N/A
67 -
54 +If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
55 +
68 68  == 7. Silent demonstration video ==
69 69  
70 70  N/A