Skip to content

Commit 9f11422

Browse files
authored
deleting duplicate word
1 parent 5dc273b commit 9f11422

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/iot-edge/troubleshoot-common-errors.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ Be sure to set this configuration for the *edgeAgent* and *edgeHub* modules as w
125125

126126
If IoT Edge is installed as a snap, use the `--container-engine-config-file` parameter to specify the location of the Docker configuration file. For example, if the Docker configuration file is located at `/var/snap/docker/current/config/daemon.json`, run the following command: `iotedge check --container-engine-config-file '/var/snap/docker/current/config/daemon.json'`.
127127

128-
Currently, the warning message continues to appear in the output of *iotedge check* even after you've set the configuration file location. Check reports the error because the IoT Edge snap doesn't have read access to the Docker snap. If you use *iotedge check* in your release process, you can suppress the the warning message by using the `--ignore container-engine-dns container-engine-logrotate` parameter.
128+
Currently, the warning message continues to appear in the output of *iotedge check* even after you've set the configuration file location. Check reports the error because the IoT Edge snap doesn't have read access to the Docker snap. If you use *iotedge check* in your release process, you can suppress the warning message by using the `--ignore container-engine-dns container-engine-logrotate` parameter.
129129

130130
### Edge Agent module with LTE connection reports 'empty edge agent config' and causes 'transient network error'
131131

0 commit comments

Comments
 (0)