-
Notifications
You must be signed in to change notification settings - Fork 60
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
Can't start any two docker-compose environments after update to Windows 20H2 #140
Comments
I'll get this issue assigned to the proper team soon. |
This issue has been open for 30 days with no updates. |
8 similar comments
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
Sorry for the delay @stephen-turner, is this still an issue you're facing? |
Thanks for reaching out. I assume it's still present unless some effort has been made to fix it, but I'm not actually the original reporter, I just transferred it from docker/for-win#9999. The OR is @marcusschroeder. |
This issue has been open for 30 days with no updates. |
1 similar comment
This issue has been open for 30 days with no updates. |
I don't know what the status of this is since I moved teams. Changed the assignment to @fady-azmy-msft. |
This issue has been open for 30 days with no updates. |
1 similar comment
This issue has been open for 30 days with no updates. |
Apologies for the radio silence. We have been able to reproduce the issue, and are looking into this. I've also created an internal ticket (41698313) to track this internally. |
This issue has been open for 30 days with no updates. |
This issue has been open for 30 days with no updates. |
Good news coming soon 🎉 |
This issue has been open for 30 days with no updates. |
@ntrappe-msft super excited to hear that good news - any updates? |
Hi, I totally understand how important this is to fix asap. @MikeZappa87 do you have any updates? You know more about the status of this Issue than I do. |
This issue has been open for 30 days with no updates. |
I'm also very keen to get this fixed. Has there been any progress - this is pretty core functionality. |
This issue has been open for 30 days with no updates. |
1 similar comment
This issue has been open for 30 days with no updates. |
Reassigning Issue to another dev. |
This issue has been open for 30 days with no updates. |
@ntrappe-msft, has there been any progress on this? It's been over half a year since "good news" was supposedly coming soon. |
@sikhness, we're actively working on this. It’s taking a bit longer than expected, will post any updates here. |
Thanks @adrianm-msft, we're eagerly awaiting news! |
@sikhness, it looks like rolling back to windows 1903 temporarily fixes the issue until a windows update is applied again. |
Thanks @adrianm-msft, this won't be possible in my environment as my host is running Windows Server 2022 and I don't think it can rollback to a version that old. |
Using 2019 also helps. Not that I would recommend that, but indeed it still works there. |
I would love to see this issue resolved as well. I've spent countless hours trying to debug the application logic and the docker setup on my Windows Server 2022 machine only to find that the problem is in fact the above. For those looking for a temporary workaround (and I appreciate that this won't apply to more complex setups!), simplifying the networking stack in the compose file resolved all my issues with the containers sporadically hanging during startup, having to restart the docker service and in some cases the entire system etc. Specifically, I removed the custom networks and customised the default one instead to prevent having multiple networks (default network was being created automatically). I'm only mentioning this here to aid those who also struggled with the same problem in a hope it gets more visibility online. |
Hey @marceliwac, |
@sikhness I'm afraid the workaround I use wouldn't be of help in this case. All I do is change the If I recall correctly, when looking for the solution to this issue I stumbled upon a few threads which mentioned the same (or adjacent) issues you are facing. The solution involved setting a static MAC address for the HyperV NAT Virtual Adapter. I'm sorry I cannot give you anything more concrete, but here are few links that might be worth looking at. They are not exactly answers to your question but might give you some ideas: https://superuser.com/questions/1701567/how-to-add-a-static-ip-adress-to-a-virtual-machine-in-hyper-v-to-stop-changing-t |
This issue has been open for 30 days with no updates. |
That woulkd be indeed awesome. It seems as if this breaks a lot of stuff for enough people. |
This was originally filed by user @marcusschroeder as docker/for-win#9999, but as it can be reliably reproduced on Windows 2010 (maybe 2004?) but not 1903, and as it only happens with Windows containers, we believe that it is a bug in the windows container code.
Original report:
My colleague @StefanScherer has reproduced it without docker compose, but with a second nat network as follows:
The text was updated successfully, but these errors were encountered: