Updated README.md.

README.md

@@ -52,26 +52,27 @@ This file is generated by the command below into the <b>empty</b> mounted folder
 > chmod 666
 >```
 
+> <span style="color:yellow;"> **Note:** </span> <br>
+> Attention there is a discrepancy between the default configuration of azureiotedge-agent in the cloud (currently v1.4) and the configuration in the device. (v1.1). <br>
+> If you are not careful, two images are downloaded, which leads to <strong>"no space on device"</strong> problems.
+> The workaround is to keep the configurations the same. e.g. after the <br>
+> ```bash
+> docker run --rm -v /config:/config wagoautomation/azure-iot-edge init
+>```
+>, synchronize the configuration manually.
+> 
+ 
+
 Finally, provisioning configurations can be made by editing the corresponding sections in config.yaml (e.g. manual provisioning using connection string or X.509 certificate)
 For more details see: https://docs.microsoft.com/en-us/azure/iot-edge/how-to-manual-provision-symmetric-key?tabs=azure-portal%2Clinux
 
  ```bash
   docker run -d --name azure-iot-edge-runtime \
     --restart=unless-stopped \
     -v /var/run/docker.sock:/var/run/docker.sock \
-    -v /usr/bin/docker:/usr/bin/docker \   
-    -v /etc/docker:/etc/docker \
     -v /config:/config:ro \
     wagoautomation/azure-iot-edge
   ```
->If you are using a Windows WSL2 linux distribution with the Docker >Desktop integration you have to replace the bind mount:
->```bash
->-v /usr/bin/docker:/usr/bin/docker
->```
->with  
->```bash
->-v /usr/bin/com.docker.cli:/usr/bin/docker
->```
 
 After the container start, all deployments defined in Microsoft Azure are automatically downloaded and started. 
 <br>This may take a few minutes.