-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
runtime-extra-platforms rolling build failure: Docker Internal Server Error - The container operating system does not match the host operating system. #67728
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsSeen in the two latest rolling builds from
Both rolling builds had a general problem causing most tests to output this to the log:
The run_client.py log from artifacts show this:
@MattGal @danmoseley @ilyas1974
|
To keep you in the loop, this is what I found - "It depends on the isolation type being used. On Windows Server, process isolation is used by default. With process isolation, the host and container must be the same version. With Hyper-V isolation, the container can be the same version or a lower version than the host. This is described at https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility with some helpful tables." I've created dotnet/arcade#8981 to investigate |
Continues affecting the 308 failures: https://dev.azure.com/dnceng/public/_build/results?buildId=1706951&view=results |
Continues happening on runtime-extra-platforms consistently:
|
Seems to be occurring on #68615 regularly. |
Note that #68615 failures were not on Windows Server 2022:
|
I think we have a bug from the other attempted fix; I'm trying some stuff and will reply back shortly. |
Rolling back the change that added hyper-v isolation calls seems to have unblocked this. |
Closing as per above. |
@MattGal Is the original issue that the hyper-v isolation was trying to fix expected to still be occurring? I'm having trouble tracking if it was fixed again after the rollback. A number of runs are erroring with From a recent test result:
In runclient.py.
|
@elinor-fung that IS the original issue I believe that it was trying to address; let me poke around and see if there's a less universally-breaking way to unblock you. As a side note, did you know that Windows 20H1 (i.e. 2004) has been end of life since December 2021? I think just removing that might simplify things. |
Oh, that sounds like a thing we should do. @dotnet/runtime-infrastructure is there a specific reason we use this version (for libraries-coreclr outerloop and for runtime-extra-platforms)? Or should we be moving to some newer Windows Server Core? |
@elinor-fung I verified that |
Sorry, I think I misunderstood what @MattGal was saying above, and I can see that this issue is not actually fixed on runtime-extra-platforms. All win-x64 runs there are failing with the issue in the original post. We also have the
Based on the discussions above it seems to me that we should move to a newer OS. |
Yup, moving to a newer OS sounds good. I don't know of any blockers for this, so we should go ahead and do it ASAP. I've started trying to build a list of the configurations we run on in https://github.com/dotnet/runtime/blob/main/docs/infra/test-configurations.md, so we can easily audit (and note any reasons why we're on that image, if necessary). |
@ilyas1974 is this maybe something that Matrix of Truth could help with? |
While I don't think would be something we add to the Matrix of Truth, I think it is something that we want to include in https://github.com/dotnet/core-eng/issues/6708. |
Issue continues happening on runtime-extra-platforms consistently in all builds (last one here ) From logs I can see "ERROR dockerhelper(233) run API Error attempting to talk to Docker Server:500 Server Error: Internal Server Error ("CreateComputeSystem 3eabe1175e89e82cc6ee266148d8b4c2d2281ef651a0bc2082e1200f573c43fd: The container operating system does not match the host operating system." |
Seen in the two latest rolling builds from
runtime-extra-platforms
:Both rolling builds had a general problem causing most tests to output this to the log:
The run_client.py log from artifacts show this:
@MattGal @danmoseley @ilyas1974
The text was updated successfully, but these errors were encountered: