Adhjie · December 13, 2024 10:42 · Nov 30, 2021 · Nov 30, 2021 · Nov 30, 2021 · Nov 30, 2021
diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -234,4 +234,5 @@ See [Setting Up Docker for Windows and WSL to Work Flawlessly](https://nickjanet
   * I do not know why it is so. Despite `docker.exe` is just client to `dockerd` in WSL, but it makes some difference. When we use  not-patched version of `docker.exe` then `/etc/hosts` does not contains needed alias. But when we use patched version of `docker.exe` from Docker Desktop (with required `com.docker.cli.exe`) then it gets OK. I suggested that a problem is hidden in difference of versions and checked it. Probably, Nope. 
      * `Docker 20.10.10, build b485636` from Docker Desktop
      * `Docker 20.10.9, build c2ea9bc` from binaries
+     * `Docker 20.10.10, build b485636` from binaries
   * At the same time do not touch `docker-compose.exe`, leave original version
diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -233,5 +233,5 @@ See [Setting Up Docker for Windows and WSL to Work Flawlessly](https://nickjanet
   * Then make steps above to unpack binaries. Then copy with a replace files `docker.exe` and `com.docker.cli.exe` from `c:\Program Files\Docker_\Docker\resources\bin\` to `c:\Program Files\Docker`. 
   * I do not know why it is so. Despite `docker.exe` is just client to `dockerd` in WSL, but it makes some difference. When we use  not-patched version of `docker.exe` then `/etc/hosts` does not contains needed alias. But when we use patched version of `docker.exe` from Docker Desktop (with required `com.docker.cli.exe`) then it gets OK. I suggested that a problem is hidden in difference of versions and checked it. Probably, Nope. 
      * `Docker 20.10.10, build b485636` from Docker Desktop
-     * `Docker version 20.10.9, build c2ea9bc` from binaries
+     * `Docker 20.10.9, build c2ea9bc` from binaries
   * At the same time do not touch `docker-compose.exe`, leave original version
diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -231,7 +231,7 @@ See [Setting Up Docker for Windows and WSL to Work Flawlessly](https://nickjanet
   The only way to fix it was found:
   * Install Docker Desktop and clone folder `c:\Program Files\Docker` as `c:\Program Files\Docker_`. After that Docker Desktop can be removed.
   * Then make steps above to unpack binaries. Then copy with a replace files `docker.exe` and `com.docker.cli.exe` from `c:\Program Files\Docker_\Docker\resources\bin\` to `c:\Program Files\Docker`. 
-  * I do not know why it is so. Despite `docker.exe` is just client to `dockerd` in WSL, but it makes some difference. When we use  not-patched version of `docker.exe` then `/etc/hosts` does not contains needed alias. But when we use patched version of `docker.exe` from Docker Desktop (with required `com.docker.cli.exe`) then it gets OK. I suggested that a problem is hidden in difference of versions and checked it. Nope. 
+  * I do not know why it is so. Despite `docker.exe` is just client to `dockerd` in WSL, but it makes some difference. When we use  not-patched version of `docker.exe` then `/etc/hosts` does not contains needed alias. But when we use patched version of `docker.exe` from Docker Desktop (with required `com.docker.cli.exe`) then it gets OK. I suggested that a problem is hidden in difference of versions and checked it. Probably, Nope. 
      * `Docker 20.10.10, build b485636` from Docker Desktop
-     * 
+     * `Docker version 20.10.9, build c2ea9bc` from binaries
   * At the same time do not touch `docker-compose.exe`, leave original version
diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -226,11 +226,11 @@ pip3 install --user docker-compose
 
 See [Setting Up Docker for Windows and WSL to Work Flawlessly](https://nickjanetakis.com/blog/setting-up-docker-for-windows-and-wsl-to-work-flawlessly)
 
-# :radioactive: Problem with `host.docker.internal:6006`
+# :radioactive: Problem with `host.docker.internal`
   > I caught error `Error: net::ERR_CONNECTION_REFUSED at http://host.docker.internal:6006?path=...` with `docker-chromium` having run under `jet-puppeteer-docker` in Jetbrains Idea (only there).
   The only way to fix it was found:
   * Install Docker Desktop and clone folder `c:\Program Files\Docker` as `c:\Program Files\Docker_`. After that Docker Desktop can be removed.
-  * Then make steps above to unpack binaries `docker.exe` with `com.docker.cli.exe` from `c:\Program Files\Docker_\Docker\resources\bin\` to `c:\Program Files\Docker`. 
+  * Then make steps above to unpack binaries. Then copy with a replace files `docker.exe` and `com.docker.cli.exe` from `c:\Program Files\Docker_\Docker\resources\bin\` to `c:\Program Files\Docker`. 
   * I do not know why it is so. Despite `docker.exe` is just client to `dockerd` in WSL, but it makes some difference. When we use  not-patched version of `docker.exe` then `/etc/hosts` does not contains needed alias. But when we use patched version of `docker.exe` from Docker Desktop (with required `com.docker.cli.exe`) then it gets OK. I suggested that a problem is hidden in difference of versions and checked it. Nope. 
      * `Docker 20.10.10, build b485636` from Docker Desktop
      * 

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -224,4 +224,14 @@ pip3 install --user docker-compose
   ```
   See also [link1](https://github.com/docker/compose/issues/6339#issuecomment-506561297), [link2](https://fantashit.com/typeerror-load-config-got-an-unexpected-keyword-argument-config-dict/), [link3](https://archived.forum.manjaro.org/t/docker-compose-seems-broken-on-kyria/127653)
 
-See [Setting Up Docker for Windows and WSL to Work Flawlessly](https://nickjanetakis.com/blog/setting-up-docker-for-windows-and-wsl-to-work-flawlessly)
+See [Setting Up Docker for Windows and WSL to Work Flawlessly](https://nickjanetakis.com/blog/setting-up-docker-for-windows-and-wsl-to-work-flawlessly)
+
+# :radioactive: Problem with `host.docker.internal:6006`
+  > I caught error `Error: net::ERR_CONNECTION_REFUSED at http://host.docker.internal:6006?path=...` with `docker-chromium` having run under `jet-puppeteer-docker` in Jetbrains Idea (only there).
+  The only way to fix it was found:
+  * Install Docker Desktop and clone folder `c:\Program Files\Docker` as `c:\Program Files\Docker_`. After that Docker Desktop can be removed.
+  * Then make steps above to unpack binaries `docker.exe` with `com.docker.cli.exe` from `c:\Program Files\Docker_\Docker\resources\bin\` to `c:\Program Files\Docker`. 
+  * I do not know why it is so. Despite `docker.exe` is just client to `dockerd` in WSL, but it makes some difference. When we use  not-patched version of `docker.exe` then `/etc/hosts` does not contains needed alias. But when we use patched version of `docker.exe` from Docker Desktop (with required `com.docker.cli.exe`) then it gets OK. I suggested that a problem is hidden in difference of versions and checked it. Nope. 
+     * `Docker 20.10.10, build b485636` from Docker Desktop
+     * 
+  * At the same time do not touch `docker-compose.exe`, leave original version
diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -207,7 +207,7 @@
   ```
   Thereby `nerdctl` can be used as `docker` but this is possible only in bash under WSL (think about how to make link or script to fix parameter).
 
-# Docker Compose
+# :heart_on_fire: Docker Compose
 ```
 sudo apt-get install -y python3 python3-pip
 pip3 install --user docker-compose

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -4,7 +4,7 @@
 * [Docker/Kubernetes Clients](https://gist.github.com/gorshkov-leonid/14c7d846d9032a756b93d4bdf01b4b07)
 * [Git tricks](https://gist.github.com/gorshkov-leonid/13f5c1df4f7484fd884af330a5974fb7)
 
-> See items marked with :heart_on_fire: to use won variants 
+> See items marked with :heart_on_fire: to use winning variants 
  
 # Docker in Windows without Docker Desktop
 ## :heart_on_fire: Way 1. Using original docker binaries

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -4,7 +4,8 @@
 * [Docker/Kubernetes Clients](https://gist.github.com/gorshkov-leonid/14c7d846d9032a756b93d4bdf01b4b07)
 * [Git tricks](https://gist.github.com/gorshkov-leonid/13f5c1df4f7484fd884af330a5974fb7)
 
-
+> See items marked with :heart_on_fire: to use won variants 
+ 
 # Docker in Windows without Docker Desktop
 ## :heart_on_fire: Way 1. Using original docker binaries
 ### Install docker client in Windows

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -59,7 +59,7 @@
     ``` 
     </details> 
 
-    :arrow_heading_down: **Run docker daemon on Windows startup using Task Scheduler (taskschd.msc)**
+    :arrow_heading_down: :heart_on_fire: **Run docker daemon on Windows startup using Task Scheduler (taskschd.msc)**
     ```powershell
     $task = New-ScheduledTaskAction -Execute "C:\Windows\System32\wsl.exe" -Argument '-u root bash -c "(source /etc/profile && rundocker &) && sleep 10"'
     $trigger = New-ScheduledTaskTrigger -AtLogon

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -6,7 +6,7 @@
 
 
 # Docker in Windows without Docker Desktop
-## Way 1. Using original docker binaries
+## :heart_on_fire: Way 1. Using original docker binaries
 ### Install docker client in Windows
 * Download necessary version of docker binaries from https://docs.docker.com/engine/install/binaries/ and extract archive to `c:/Program Files`, for example, using script in powershell. Run powershell as Administrator and call:
   ```powershell
@@ -21,7 +21,7 @@
   ```powershell
   [Environment]::SetEnvironmentVariable("Path",$env:Path + ";c:/Program Files/docker", "Machine")
   ```
-### Install Docker Daemon in WSL
+### :heart_on_fire: Install Docker Daemon in WSL
 * Install docker under Ubuntu WSL using these instructions https://docs.docker.com/engine/install/ubuntu/
 * [To provide ability](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) to call `docker` in WSL without `sudo` add current user to `docker` group
   ```bash

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -211,8 +211,16 @@
 sudo apt-get install -y python3 python3-pip
 pip3 install --user docker-compose
 ```
-> Do not forget to set variable DOCKER_HOST in `~/.bashrc` if it has not still done.
+  :warning: Do not forget to set variable DOCKER_HOST in `~/.bashrc` if it has not still done.
   ```
   export DOCKER_HOST=tcp://localhost:2375
   ```
+  :warning: On error `TypeError: load_config() got an unexpected keyword argument 'config_dict'` try to call scripts:
+  ```
+  pip3 uninstall docker-compose
+  pip3 uninstall docker-py docker
+  pip3 install --user -U docker-compose
+  ```
+  See also [link1](https://github.com/docker/compose/issues/6339#issuecomment-506561297), [link2](https://fantashit.com/typeerror-load-config-got-an-unexpected-keyword-argument-config-dict/), [link3](https://archived.forum.manjaro.org/t/docker-compose-seems-broken-on-kyria/127653)
+
 See [Setting Up Docker for Windows and WSL to Work Flawlessly](https://nickjanetakis.com/blog/setting-up-docker-for-windows-and-wsl-to-work-flawlessly)
diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -213,6 +213,6 @@ pip3 install --user docker-compose
 ```
 > Do not forget to set variable DOCKER_HOST in `~/.bashrc` if it has not still done.
   ```
-  export DOCKER_HOST=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2}'):2375
+  export DOCKER_HOST=tcp://localhost:2375
   ```
 See [Setting Up Docker for Windows and WSL to Work Flawlessly](https://nickjanetakis.com/blog/setting-up-docker-for-windows-and-wsl-to-work-flawlessly)
diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -211,4 +211,8 @@
 sudo apt-get install -y python3 python3-pip
 pip3 install --user docker-compose
 ```
+> Do not forget to set variable DOCKER_HOST in `~/.bashrc` if it has not still done.
+  ```
+  export DOCKER_HOST=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2}'):2375
+  ```
 See [Setting Up Docker for Windows and WSL to Work Flawlessly](https://nickjanetakis.com/blog/setting-up-docker-for-windows-and-wsl-to-work-flawlessly)
diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -206,3 +206,9 @@
   ```
   Thereby `nerdctl` can be used as `docker` but this is possible only in bash under WSL (think about how to make link or script to fix parameter).
 
+# Docker Compose
+```
+sudo apt-get install -y python3 python3-pip
+pip3 install --user docker-compose
+```
+See [Setting Up Docker for Windows and WSL to Work Flawlessly](https://nickjanetakis.com/blog/setting-up-docker-for-windows-and-wsl-to-work-flawlessly)
diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -50,7 +50,9 @@
 
     <details>
     <summary>Details...</summary>
+
     :warning: Be aware of this warnings:
+
     ```
     Binding to IP address without --tlsverify is insecure and gives root access on this machine to everyone who has access to your network.  host="tcp://172.27.117.140:2375"
     Binding to an IP address, even on localhost, can also give access to scripts run in a browser. Be safe out there!  host="tcp://172.27.117.140:2375"

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -81,9 +81,11 @@
     rundocker &
     ```   
   :point_right:  **without access from Windows, using systemd**  
-
+    
     :warning: this method raises questions. Firstly, I do not know how to get access from Windows, e.g. cmd.exe. Secondly, `systemd` is a kind of overhead.
 
+    :warning: TBD try to enable systemd: https://youtu.be/DmfuJzX6vJQ?t=459
+
     :arrow_heading_down: **Add systemd support ([about script](https://gist.github.com/djfdyuruiry/6720faa3f9fc59bfdf6284ee1f41f950), [about Linux Software Repository for Microsoft Products](https://docs.microsoft.com/ru-ru/windows-server/administration/linux-package-repository-for-microsoft-software))**
 
     ```bash

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -174,7 +174,7 @@
 
   TBD
 
-## Way 2. Using of `nerdctl` from [Rancher Desktop](https://github.com/rancher-sandbox/rancher-desktop) instead of docker
+## Way 2. Using `nerdctl` from [Rancher Desktop](https://github.com/rancher-sandbox/rancher-desktop) instead of docker
 
 :warning: this way is not completely functional. Firstly, I do knot know how to make `docker` available everywhere - not only in bash under WSL. Secondly, `nerdctl` is not `docker`, so it could bring unexpected problems (e.g. `nerdctl` does not have `--ip` param for `nerdctl run`, who knows what else difference exist). But Rancher Desktop can be used as separate container orchestrator.
 

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -2,6 +2,7 @@
 * [Install application](https://gist.github.com/gorshkov-leonid/f7507539c9ddd7ac38741692f149c692)
 * **[Docker in Windows without Docker Desktop](#)**
 * [Docker/Kubernetes Clients](https://gist.github.com/gorshkov-leonid/14c7d846d9032a756b93d4bdf01b4b07)
+* [Git tricks](https://gist.github.com/gorshkov-leonid/13f5c1df4f7484fd884af330a5974fb7)
 
 
 # Docker in Windows without Docker Desktop

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -34,7 +34,6 @@
     :arrow_heading_down: **Edit `/etc/profile`**
 
     ```bash
-    ## Use this variant in case when `localhostForwarding` in `/etc/wsl.conf` is equal to `true`
     function rundocker(){
       ## Use this variant in case when `localhostForwarding` in `/etc/wsl.conf` is unset or equal to `false`
       #DOCKER_HOST=`ifconfig eth0 | grep -E "inet ([0-9]{1,3}.){3}[0-9]{1,3}" | head -1 | awk '{ print $2 }'`

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -34,11 +34,9 @@
     :arrow_heading_down: **Edit `/etc/profile`**
 
     ```bash
-    ## Use this variant in case when `localhostForwarding` in `/etc/wsl.conf` is unset or equal to `false`
-    #export DOCKER_HOST=`ifconfig eth0 | grep -E "inet ([0-9]{1,3}.){3}[0-9]{1,3}" | head -1 | awk '{ print $2 }'`
-
     ## Use this variant in case when `localhostForwarding` in `/etc/wsl.conf` is equal to `true`
     function rundocker(){
+      ## Use this variant in case when `localhostForwarding` in `/etc/wsl.conf` is unset or equal to `false`
       #DOCKER_HOST=`ifconfig eth0 | grep -E "inet ([0-9]{1,3}.){3}[0-9]{1,3}" | head -1 | awk '{ print $2 }'`
       DOCKER_HOST=localhost
       WIN_CLIENT="/mnt/c/Program Files/docker/docker.exe"

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -180,7 +180,7 @@
 
 :warning: this way is not completely functional. Firstly, I do knot know how to make `docker` available everywhere - not only in bash under WSL. Secondly, `nerdctl` is not `docker`, so it could bring unexpected problems (e.g. `nerdctl` does not have `--ip` param for `nerdctl run`, who knows what else difference exist). But Rancher Desktop can be used as separate container orchestrator.
 
-:warning: I run `nerdctl -n docker  run -p 3000:3000 grafana/grafana`, checked and then stopped container via ctrl+c. After it, I cannot run it again until rebooting.
+:warning: I run `nerdctl -n docker  run -p 3000:3000 grafana/grafana`, checked and then stopped container via ctrl+c or stop. After it, I cannot run it again until rebooting.
 
 * Install `Rancher Desktop`
 * Run and choose some version of Kubernetes

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -180,6 +180,8 @@
 
 :warning: this way is not completely functional. Firstly, I do knot know how to make `docker` available everywhere - not only in bash under WSL. Secondly, `nerdctl` is not `docker`, so it could bring unexpected problems (e.g. `nerdctl` does not have `--ip` param for `nerdctl run`, who knows what else difference exist). But Rancher Desktop can be used as separate container orchestrator.
 
+:warning: I run `nerdctl -n docker  run -p 3000:3000 grafana/grafana`, checked and then stopped container via ctrl+c. After it, I cannot run it again until rebooting.
+
 * Install `Rancher Desktop`
 * Run and choose some version of Kubernetes
 * Tick `WSL Integration -> Ubuntu`. Link `/home/<wsl-user>/.kube/config -> /mnt/c/Users/<win-user>/.kube/config` will be created.

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -178,7 +178,7 @@
 
 ## Way 2. Using of `nerdctl` from [Rancher Desktop](https://github.com/rancher-sandbox/rancher-desktop) instead of docker
 
-:warning: this way is not completely functional. Firstly, I do knot know how to make `docker` available everywhere - not only in bash under WSL. Secondly, `nerdctl` is not `docker`, so it could bring unexpected problems. But Rancher Desktop can be used as separate container orchestrator.
+:warning: this way is not completely functional. Firstly, I do knot know how to make `docker` available everywhere - not only in bash under WSL. Secondly, `nerdctl` is not `docker`, so it could bring unexpected problems (e.g. `nerdctl` does not have `--ip` param for `nerdctl run`, who knows what else difference exist). But Rancher Desktop can be used as separate container orchestrator.
 
 * Install `Rancher Desktop`
 * Run and choose some version of Kubernetes

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -83,7 +83,9 @@
     rundocker &
     ```   
   :point_right:  **without access from Windows, using systemd**  
+
     :warning: this method raises questions. Firstly, I do not know how to get access from Windows, e.g. cmd.exe. Secondly, `systemd` is a kind of overhead.
+
     :arrow_heading_down: **Add systemd support ([about script](https://gist.github.com/djfdyuruiry/6720faa3f9fc59bfdf6284ee1f41f950), [about Linux Software Repository for Microsoft Products](https://docs.microsoft.com/ru-ru/windows-server/administration/linux-package-repository-for-microsoft-software))**
 
     ```bash
@@ -175,7 +177,9 @@
   TBD
 
 ## Way 2. Using of `nerdctl` from [Rancher Desktop](https://github.com/rancher-sandbox/rancher-desktop) instead of docker
+
 :warning: this way is not completely functional. Firstly, I do knot know how to make `docker` available everywhere - not only in bash under WSL. Secondly, `nerdctl` is not `docker`, so it could bring unexpected problems. But Rancher Desktop can be used as separate container orchestrator.
+
 * Install `Rancher Desktop`
 * Run and choose some version of Kubernetes
 * Tick `WSL Integration -> Ubuntu`. Link `/home/<wsl-user>/.kube/config -> /mnt/c/Users/<win-user>/.kube/config` will be created.

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -82,15 +82,6 @@
     ```
     rundocker &
     ```   
-
-  :point_right: **over https with access from Windows too**
-
-  TBD
-
-  :point_right:  **over channels?**
-
-  TBD
-
   :point_right:  **without access from Windows, using systemd**  
     :warning: this method raises questions. Firstly, I do not know how to get access from Windows, e.g. cmd.exe. Secondly, `systemd` is a kind of overhead.
     :arrow_heading_down: **Add systemd support ([about script](https://gist.github.com/djfdyuruiry/6720faa3f9fc59bfdf6284ee1f41f950), [about Linux Software Repository for Microsoft Products](https://docs.microsoft.com/ru-ru/windows-server/administration/linux-package-repository-for-microsoft-software))**
@@ -174,6 +165,15 @@
     ```
     C:\Windows\System32\wsl.exe genie -s
     ```  
+
+  :point_right: **over https with access from Windows too**
+
+  TBD
+
+  :point_right:  **over channels?**
+
+  TBD
+
 ## Way 2. Using of `nerdctl` from [Rancher Desktop](https://github.com/rancher-sandbox/rancher-desktop) instead of docker
 :warning: this way is not completely functional. Firstly, I do knot know how to make `docker` available everywhere - not only in bash under WSL. Secondly, `nerdctl` is not `docker`, so it could bring unexpected problems. But Rancher Desktop can be used as separate container orchestrator.
 * Install `Rancher Desktop`

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -5,7 +5,7 @@
 
 
 # Docker in Windows without Docker Desktop
-## Way 1. Using original docker images.
+## Way 1. Using original docker binaries
 ### Install docker client in Windows
 * Download necessary version of docker binaries from https://docs.docker.com/engine/install/binaries/ and extract archive to `c:/Program Files`, for example, using script in powershell. Run powershell as Administrator and call:
   ```powershell

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -175,7 +175,7 @@
     C:\Windows\System32\wsl.exe genie -s
     ```  
 ## Way 2. Using of `nerdctl` from [Rancher Desktop](https://github.com/rancher-sandbox/rancher-desktop) instead of docker
-:warning: this way is not completely functional. Firstly, I do knot know how to make `docker` available everywhere - not only in bash under WSL. Secondly, `nerdctl` is not `docker`, so it could bring unexpected problems.
+:warning: this way is not completely functional. Firstly, I do knot know how to make `docker` available everywhere - not only in bash under WSL. Secondly, `nerdctl` is not `docker`, so it could bring unexpected problems. But Rancher Desktop can be used as separate container orchestrator.
 * Install `Rancher Desktop`
 * Run and choose some version of Kubernetes
 * Tick `WSL Integration -> Ubuntu`. Link `/home/<wsl-user>/.kube/config -> /mnt/c/Users/<win-user>/.kube/config` will be created.

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -92,7 +92,7 @@
   TBD
 
   :point_right:  **without access from Windows, using systemd**  
-    :warning: this methodhas restrictions. At first, I do know how to get access from window, e.g. cnd.exe. Secondly, systemd looks like overhead.
+    :warning: this method raises questions. Firstly, I do not know how to get access from Windows, e.g. cmd.exe. Secondly, `systemd` is a kind of overhead.
     :arrow_heading_down: **Add systemd support ([about script](https://gist.github.com/djfdyuruiry/6720faa3f9fc59bfdf6284ee1f41f950), [about Linux Software Repository for Microsoft Products](https://docs.microsoft.com/ru-ru/windows-server/administration/linux-package-repository-for-microsoft-software))**
 
     ```bash

diff --git a/docker-in-windows.md b/docker-in-windows.md
@@ -92,7 +92,7 @@
   TBD
 
   :point_right:  **without access from Windows, using systemd**  
-
+    :warning: this methodhas restrictions. At first, I do know how to get access from window, e.g. cnd.exe. Secondly, systemd looks like overhead.
     :arrow_heading_down: **Add systemd support ([about script](https://gist.github.com/djfdyuruiry/6720faa3f9fc59bfdf6284ee1f41f950), [about Linux Software Repository for Microsoft Products](https://docs.microsoft.com/ru-ru/windows-server/administration/linux-package-repository-for-microsoft-software))**
 
     ```bash
@@ -175,7 +175,7 @@
     C:\Windows\System32\wsl.exe genie -s
     ```  
 ## Way 2. Using of `nerdctl` from [Rancher Desktop](https://github.com/rancher-sandbox/rancher-desktop) instead of docker
-:warning: this way is not fully functional. Firstly, I do knot know how to make `docker` available everywhere - not only in bash under WSL. Secondly, `nerdctl` is not `docker`, so it could bring unexpected problems.
+:warning: this way is not completely functional. Firstly, I do knot know how to make `docker` available everywhere - not only in bash under WSL. Secondly, `nerdctl` is not `docker`, so it could bring unexpected problems.
 * Install `Rancher Desktop`
 * Run and choose some version of Kubernetes
 * Tick `WSL Integration -> Ubuntu`. Link `/home/<wsl-user>/.kube/config -> /mnt/c/Users/<win-user>/.kube/config` will be created.
No results found