-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DCOM not working in windows #6314
Comments
Is DCOM (wmic) to the host expected to work in Windows containers, when not using host network? I'm not seeing how this issue is unique to RKE2. Can Microsoft confirm that this is even supposed to be supported? |
With docker desktop it is working |
Docker Desktop isn't Kubernetes? |
One more information 6 months back even RKE2 it works with 2019 but not 2022. At that time we used 1.24* version with calico CNI |
@brandond any update on this? |
No, I don't know enough about how DCOM connects to hosts over the container network to even begin suggesting where the problem lies. Did MS have any ideas, other than pointing their finger at the CNI? |
@brandond Apart from DCOM I did some analysis found below network issue. I have a application which is hosting a WCF service on a port 9500 and it is running in a windows container. If I try to access the service from another windows container. APITest is test application to access the service. To make it more simple i have used windows PowerShell script command for RPC the port 135 should be accessible. So I tried the same for port 135 the result are same, through service IP it is failing. If I do the same hosting a service in linux container and try to access from another windows container all 3 combinations succeeded. So there must some network issue when a service is running in windows container |
@brandond any update on the network issue when using service IP and port |
Environmental Info:
RKE2 Version:
v1.30.1
Node(s) CPU architecture, OS, and Version:
Cluster 1
3 Linux nodes - master - RHEL 8
1 windows - agent - Window server 2022
Cni: flannel
Cluster 2
3 Linux nodes - master - RHEL 8
2 windows - agent - Window server 2019
Cni: flannel
Describe the bug:
Our application is trying to connect a DCOM server from this windows containers.
We are getting RPC unavailable error.
We are using mcr.microsoft.com/dotnet/aspnet:8.0.6-windowsservercore-ltsc2022
We raised Microsoft ticket regarding this but looks like it is related to RKE2 network. Because if I change the network mode to host it is working where as in Cluster mode it is not working
Steps To Reproduce:
wmic /node:**<any windows server Ip>** os get caption
Expected behavior:
Caption
Microsoft Windows Server 2022 Standard
Actual behavior:
ERROR:
Description = The RPC server is unavailable.
The text was updated successfully, but these errors were encountered: