Can't deploy modules on Windows
See original GitHub issueExpected Behavior
Deployment/redeployment of a module should work reliably.
Current Behavior
New module or new module version is not deployed
Steps to Reproduce
- Have a deployment running
- Update one of the modules (like change the image URI) through the deployment manifest
- The updated module is not started up on the edge device
Context (Environment)
Device (Host) Operating System
Windows Server 2019
Architecture
amd64
Container Operating System
Windows containers
Runtime Versions
iotedged
iotedge 1.0.7~rc2 (03dff5f270fabe34e7903c04e334dca2665780a6)
Edge Agent
1.0.7
Edge Hub
1.0.7
Docker
Client: Version: 3.0.2 API version: 1.40 Go version: go1.11.1 Git commit: e042b58f Built: Tue Dec 4 20:13:19 2018 OS/Arch: windows/amd64 Experimental: false
Server: Engine: Version: 3.0.3 API version: 1.40 (minimum version 1.24) Go version: go1.11.4 Git commit: 5ec3138 Built: Thu Jan 24 17:16:18 2019 OS/Arch: windows/amd64 Experimental: false
Logs
https://gist.github.com/mbialecka/5b479750b70148b0dbbf44f0e5164870
Additional Information
First two deployments after environment startup worked fine. Then, after a couple of hours, the third deployment didn’t go through, it should have happened around 2019-05-13 08:02 mark. Instead, there are many timeout errors in the edgeAgent log.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (2 by maintainers)
Top GitHub Comments
As the connectivity checks suggest, your edge device has connectivity issues from within the container environment. Please follow best practices here as documented at https://aka.ms/iotedge-prod-checklist-dns (recommend Option 1).
Confirm the connectivity checks pass, and then perform your testing.
Hello,
Which dns have you used to resolve connectivity issues from your containers to iothub ?
I am trying to install iotedge runtime behind a proxy as well but i still have different issues including connectivity from containers to Iothub,the host can connect still.
Thanks