ghost
commented
11 months ago Tagging subscribers to this area: @dotnet/ncl See info in area-owners.md if you want to be subscribed.
Issue Details
### Description I've created an IoTEdge module, which is an application containerized using Docker, and initially, it was built with dotnet core version 3.1. We've been using this module for a considerable amount of time. However, as part of our security team's recommendations, we decided to migrate it to dotnet core version 7.0. After making this migration, we encountered a System.Net.Socket.SocketException when running the modules. We attempted to test it with dotnet core 6.0 as well, but unfortunately, we faced the same issue. Consequently, we reverted the Docker base image back to version 3.1, and the module started functioning correctly. I'm sharing the exception details for additional information. ``` {"logsource":"ddiotdevicehostmodule","logdata":"Message:-Initializing IoT Hub module client;CallingMemberName:-Init","loglevel":2,"logtype":4,"logtime":"2023-09-21T05:13:20.8909851+00:00","correlationId":null}, {"logsource":"ddiotdevicehostmodule","logdata":"Message:-Exception while initializing the module;CallingMemberName:-Init;Exception:-System.Net.Sockets.SocketException (10014): The system detected an invalid pointer address in attempting to use a pointer argument in a call.\r\n at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.CreateException(SocketError error, Boolean forAsyncThrow)\r\n at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ConnectAsync (Socket socket)\r\n at System.Net.Sockets.Socket.ConnectAsync(EndPoint remoteEP, CancellationToken cancellationToken)\r\n at System.Net.Sockets.Socket.ConnectAsync(EndPoint remoteEP)\r\n at Microsoft.Azure.Devices.Client.HsmAuthent ication.Transport.HttpUdsMessageHandler.GetConnectedSocketAsync()\r\n at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)\r\n at Microsoft.Azure.Devices.Client.HsmAuthentication .Transport.HttpUdsMessageHandler.GetConnectedSocketAsync()\r\n at Microsoft.Azure.Devices.Client.HsmAuthentication.Transport.HttpUdsMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)\r\n at Syst em.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)\r\n at Microsoft.Azure.Devices.Client.HsmAuthentication.Transport.HttpUdsMessageHandler.SendAsync(HttpRequestMessage request, Cancella tionToken cancellationToken)\r\n at System.Net.Http.HttpClient.
| Author: | niravjprabtani |
|---|---|
| Assignees: | - |
| Labels: | `area-System.Net.Http`, `untriaged` |
| Milestone: | - |
karelz
antonfirsov
wfurt
Description
I've created an IoTEdge module, which is an application containerized using Docker, and initially, it was built with dotnet core version 3.1. We've been using this module for a considerable amount of time. However, as part of our security team's recommendations, we decided to migrate it to dotnet core version 7.0. After making this migration, we encountered a System.Net.Socket.SocketException when running the modules. We attempted to test it with dotnet core 6.0 as well, but unfortunately, we faced the same issue. Consequently, we reverted the Docker base image back to version 3.1, and the module started functioning correctly.
We uses following docker image for our application FROM mcr.microsoft.com/dotnet/sdk:7.0
I'm sharing the exception details for additional information.
Reproduction Steps
We are not able to upgrade the application to latest dotnet core version although it works fine with dotnet core 3.1, No specific steps for reproduction
Expected behavior
Application should work as is as they works in dotnet core 3.1
Actual behavior
It gives an exceptions
Regression?
No response
Known Workarounds
No workarounds with dotnet core 7.0
Configuration
Dotnet Core 7.0 Docker Windows X64
Other information
We are using iotedge device sdk to initialize the modules. While initializing the modules we are getting this exception.