Comments (12)
I have a similar issue. Downgrading to older docker version didn't work either. Any pointers?
from iotedge.
@MPapst @gauravagarwal28 Can you share the contents of config.yaml
and output of ipconfig
from your systems?
from iotedge.
Just checked on my machine. On starting Docker I've received an update notification and installed the latest update. Test with latest version 18.06.0-ce-win72 (19098), released today, did work without any problems.
from iotedge.
# IoT Edge Daemon configuration
###############################################################################
#
# This file configures the IoT Edge daemon. The daemon must be restarted to
# pick up any configuration changes.
#
# Note - this file is yaml. Learn more here: http://yaml.org/refcard.html
#
###############################################################################
###############################################################################
# Provisioning mode and settings
###############################################################################
#
# Configures the identity provisioning mode of the daemon.
#
# Supported modes:
# manual - using an iothub connection string
# dps - using dps for provisioning
#
###############################################################################
provisioning:
source: "manual"
device_connection_string: "HostName=xxxxxx.azure-devices.net;DeviceId=mydesktopEdge;SharedAccessKey=Iwontdisclose"
# provisioning:
# source: "dps"
# global_endpoint: "https://global.azure-devices-provisioning.net"
# scope_id: "{scope_id}"
# registration_id: "{registration_id}"
###############################################################################
# Certificate settings
###############################################################################
#
# Configures the certificates required to operate the IoT Edge
# runtime as a gateway which enables external leaf devices to securely
# communicate with the Edge Hub. If not specified, the required certificates
# are auto generated for quick start scenarios which are not intended for
# production environments.
#
# Settings:
# device_ca_cert - path to the device ca certificate and its chain
# device_ca_pk - path to the device ca private key file
# trusted_ca_certs - path to a file containing all the trusted CA
# certificates required for Edge module communication
#
###############################################################################
# certificates:
# device_ca_cert: "<ADD PATH TO DEVICE CA CERTIFICATE HERE>"
# device_ca_pk: "<ADD PATH TO DEVICE CA PRIVATE KEY HERE>"
# trusted_ca_certs: "<ADD PATH TO TRUSTED CA CERTIFICATES HERE>"
###############################################################################
# Edge Agent module spec
###############################################################################
#
# Configures the initial Edge Agent module.
#
# The daemon uses this definition to bootstrap the system. The Edge Agent can
# then update itself based on the Edge Agent module definition present in the
# deployment in IoT Hub.
#
###############################################################################
agent:
name: "edgeAgent"
type: "docker"
env: {}
config:
image: "mcr.microsoft.com/azureiotedge-agent:1.0"
auth: {}
###############################################################################
# Edge device hostname
###############################################################################
#
# Configures the environment variable 'IOTEDGE_GATEWAYHOSTNAME' injected into
# modules.
#
###############################################################################
hostname: "IN-L-7010516"
###############################################################################
# Connect settings
###############################################################################
#
#
# Configures URIs used by clients of the management and workload APIs
# management_uri - used by the Edge Agent and 'iotedge' CLI to start,
# stop, and manage modules
# workload_uri - used by modules to retrieve tokens and certificates
#
# The following uri schemes are supported:
# http - connect over TCP
#
###############################################################################
connect:
management_uri: "http://10.0.75.1:15580"
workload_uri: "http://10.0.75.1:15581"
###############################################################################
# Listen settings
###############################################################################
#
# Configures the listen addresses for the daemon.
# management_uri - used by the Edge Agent and 'iotedge' CLI to start,
# stop, and manage modules
# workload_uri - used by modules to retrieve tokens and certificates
#
# The following uri schemes are supported:
# http - listen over TCP
#
###############################################################################
listen:
management_uri: "http://10.0.75.1:15580"
workload_uri: "http://10.0.75.1:15581"
###############################################################################
# Home Directory
###############################################################################
#
# This configures the home directory for the daemon.
#
###############################################################################
homedir: "C:\\ProgramData\\iotedge"
###############################################################################
# Moby Container Runtime settings
###############################################################################
#
# uri - configures the uri for the container runtime.
# network - configures the network on which the containers will be created.
#
###############################################################################
moby_runtime:
uri: "npipe://./pipe/docker_engine"
network: "nat"
from iotedge.
@veyalla: I'll check the IP's tomorrow and post it here.
from iotedge.
@MPapst Sounds good, another to check if Docker default to Linux containers after upgrade. https://docs.docker.com/docker-for-windows/#switch-between-windows-and-linux-containers
@ilyas-it83 Looks like you are working with Janice on the issues you are facing, I'll let her handle that.
from iotedge.
@ilyas-it83 one thing to note about your config file is that it is yaml and whitespace is significant. It looks like there are too many spaces before the network: "nat"
which is mostly likely causing the configuration errors you are seeing. The moby_runtime
section should look like the following:
moby_runtime:
uri: "npipe://./pipe/docker_engine"
network: "nat"
from iotedge.
@veyalla, you were right about the config.yaml. The IP of the host inside the nat
network has changed with the update from 10.0.75.1
to 172.26.48.1
.
Isn't there any way to detect that automatically when the iotedge service is starting?
Correcting the IP and the service works again.
Shall I close the issue or do you want to use as kind of feature request?
from iotedge.
PS C:\WINDOWS\system32> ipconfig
Windows IP Configuration
Ethernet adapter vEthernet (DockerNAT):
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::3902:ec8b:9a31:9b8a%4
IPv4 Address. . . . . . . . . . . : 10.0.75.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::a8f2:5021:f32b:93e0%18
IPv4 Address. . . . . . . . . . . : 10.9.43.202
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.9.43.1
Ethernet adapter vEthernet (Default Switch):
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::496c:26f8:8f39:337e%10
IPv4 Address. . . . . . . . . . . : 172.31.89.161
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . :
PS C:\WINDOWS\system32> hostname
GauravA-PC
My Config.yaml file:
((I copied it to desktop and renamed it to config.txt so that it could be uploaded here))
from iotedge.
@gauravagarwal28 can you confirm you have executed this command per the instructions (you can do it again to be sure):
Invoke-WebRequest -useb https://download.microsoft.com/download/0/6/4/064F84EA-D1DB-4EAA-9A5C-CC2F0FF6A638/vc_redist.x64.exe -o vc_redist.exe
.\vc_redist.exe /quiet /norestart
from iotedge.
@veyalla
Yes, I have executed this command too.
from iotedge.
@MPapst You are probably confusing the "nat" network used for Windows containers with "DockerNAT" network used for Linux containers. I'd guess that after the Docker for Windows update you were inadvertently switched from using Windows containers to Linux containers (or vice versa).
I am glad you were able to get it working. Please close the issue, and feel free to open a new one if you need any additional assistance.
from iotedge.
Related Issues (20)
- Configuration on unattained embedded devices HOT 4
- Protecting Edge (Docker) Module Images at rest with the IoT-Edge? HOT 3
- Microsoft.Azure.Devices.Edge.Agent.Edgelet.EdgeletCommunicationException HOT 3
- Unable to communicate with Edge modules (in EFLOW) from the host OS HOT 7
- Offline detection status / event HOT 4
- edgeAgent automatically stopping all modules HOT 1
- IoT Edge 1.4 install fails if system has users with UID 13622 / 13623 HOT 7
- IoT device works perfectly for days, then it does not - reboot fixes issue HOT 2
- Error getting device scope result from IoTHub (IotHubUnauthorizedAccess) HOT 2
- Unexpected shutdown, is it a kind of planned upgrade? HOT 4
- Direct Method of IoTEdge module takes 3 minutes to start responding HOT 11
- IoT Edge produces too much traffic with default configuration, it is not conducive for billable networks such as cellular. HOT 11
- Iotedge fails to make docker-proxy.sock after reboot (file exists) in Ubuntu Core HOT 13
- How to run aziot-edge in a docker container? HOT 10
- EdgeAgent does not restart crashed module if busy downloading new manifest 1.4.10 HOT 3
- Create a reusable Volume in Azure IOT Edge Module via Container Create Options HOT 2
- Can not ssh into a (running) VM with Ubuntu Core 20 on my k3s cluster HOT 1
- Reported twin does not reflect running container HOT 2
- Scarthgap support? HOT 1
- Best Practices/Guidance on upgrading a remote database module HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from iotedge.