Open peer-dellis opened 5 months ago
Unfortunately I am not an expert in Docker usage so that I cannot answer why windows containers should behave this way.
For reproducing the issue I miss some relevant information in the attached files or there are some inconsistencies to your description.
Sorry for the delay.
To reproduce you only need two containers running, one router and one client. They delay is seen without the 2nd client running. However to reproduce with 2 clients I created a second container with the client-program and used the command line args to give it a different net id.
This is the setup I am using![image](https://github.com/Beckhoff/TF6000_ADS_DOTNET_V5_Samples/assets/134443708/41649d9e-8940-459a-8d58-afcb67e632b0)
The use case for this setup is to be able to preform a hot swap of our software. Container 1 would be running version 1.1 of our software and container 2 startup running version 1.2. Once a handoff is completed container 2 would take over and container 1 would shutdown.
After many trial and error and support from support@beckhoff.com the above setup is working with one quirk, there is a 4000ms delay from when a client sends a request to when the router forwards the request to the PLC.
log example
The router and client console apps are based on the example code Beckhoff provides, I've attached the program.cs file. client and router.zip
I've also attached the docker images docker images.zip
I've tested the same setup with linux containers using the same container host (Win 11).
There is no delay using linux, so I assume the problem is related to using the nat driver as opposed to the bridge driver.