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
Requests with sufficiently big headers hang on hybrid swarm cluster #41332
Comments
The length of your header value is 1255 characters (1255*8=10040 bytes, assuming 8-bit). Could this be a RequestLimit on the IIS server? https://docs.microsoft.com/en-us/iis/configuration/system.webserver/security/requestfiltering/requestlimits/ does the IIS-container receive the request? Anything in the logs for that container? |
The IIS values are the following:
From the Windows machine I've used the command...
... With many more "a", but all was fine, that is: IIS work as expected. From Ubuntu, I execute the "usual" command with too many "a":
On Windows, using netstat, this is the result:
After a while (minutes, not seconds) the netstat's result is always the same. |
I have found the culprit and the workaround. Culprit: mr. MTU Workaround: see here and here. That is... 1. VM #1 (Windows):
Restart the Docker service. 2. VM #2 (Ubuntu):
Remove the old stack - if still present - and create a new one. 2. VM #2 (Ubuntu):
I've checked the issue using an hybrid swarm in...
... Without errors. |
Synopsis
On a hybrid swarm cluster (1 Ubuntu node and 1 Windows Server node) on Azure, when making an http request from a linux container (on linux node) to a windows container (on a windows node) all seems to be working fine with small size requests, but calls systematically stop working with sufficiently big headers.
Issue possibly related to the following: #41051
VM #1 (Windows)
Output of "docker version":
Output of "docker info":
VM #2 (Ubuntu)
Output of "docker version":
Output of "docker info":
That said:
VM Whiteouts in layers #2 (Ubuntu)
Execute the following command:
This should be the result:
VM Container tagging / naming #1 (Windows)
Execute the following command:
This should be the result:
VM Whiteouts in layers #2 (Ubuntu)
Execute the following command:
This should be the result:
VM Whiteouts in layers #2 (Ubuntu)
Execute the following command:
VM Container tagging / naming #1 (Windows)
Execute the following command:
VM Whiteouts in layers #2 (Ubuntu)
Create the following docker-compose, lets call it "docker-compose-test.yml":
... and then launch it:
Check that the service is up:
This should be the result:
VM Container tagging / naming #1 (Windows) : check that the service is up : docker container ls
VM Whiteouts in layers #2 (Ubuntu)
Execute the following command, keep in mind that the number of "a" is a very strict constraint:
This should be the result:
That said, when adding a sufficient amount of characters to the header, the call hangs:
The text was updated successfully, but these errors were encountered: